When to use
This name is loaded only when an existing caller specifies the legacy name; this adapter does not apply to general new requests.
This name is retained for legacy invocations. The sole rule owner is stitch-design-spec; new tasks use the new entry point directly.
Workflow
Step 1: Save the handoff input
Preserve the user request, PRD/existing specs, page/flow ID, framework, design system evidence, edit target, and delivery location; do not expand the user's scope.
Step 2: Load the unified entry point
Load the installed stitch-design-spec, passing the original input along with the output intent:prompt-only: polishing vague requirements, existing specs to prompts, or precise edits, preserving the original output scope. spec-only is a spec-trimmed view of the full contract and does not require generating a prompt first.
Step 3: Return the result
The new entry point executes its current rules; return the artifacts, assumptions, verification results, and unfinished items as-is. Forwarding itself does not equal completed delivery.
Step 4: Missing dependency recovery
If the new entry point is missing, clearly report that the dependency is not installed and preserve the context. Installation instructions:npx skills add full-stack-skills/stitch-skills --skill stitch-design-spec. Do not install automatically, and do not restore a copy of the old rules.
Rules and boundaries of non-applicability
Do not collect credentials, and do not send keys or unrelated account information downstream. This adapter does not apply to directly executing remote generation.
Validation
This entry point does not call Stitch, does not require authentication, and does not create pages, systems, or screens on its own. An existing DESIGN.md must not be upgraded into remote application evidence. Examples, legacy receipts, or tokens must not be passed as facts. Check that the target skill is loaded, the scope is consistent, and the actual results and unverified items have been returned.
Compatibility example: when the legacy name receives "generate only page specs," it forwards spec-only; when it receives "change only the search box," it forwards a local edit target and must not expand it into a full set of pages. Recovery for a missing dependency is to explain the absence and wait for the user to install it or use an existing available entry point, not to silently call remote tools.
Gotchas
- The legacy name is a discovery entry point, not a Python/CLI/MCP tool; do not treat the skill name as a remote tool invocation.
- When the user provides both the legacy name and a complete design spec, forward the spec directly to avoid re-deriving and changing the original page ID.
- When downstream returns partial results or items pending confirmation, the compatibility entry point preserves those states and must not rewrite them as "all complete."
- If the call chain goes from canonical back to this adapter, stop the loop and return to the current stage of canonical.
Source and migration
The original prompt enhancement includes Apache-2.0 content from Google LLC and contributors, which has been migrated into stitch-design-spec; the original license is retained at LICENSE.txt. Upstream pinned snapshot is a community source and not an officially supported product.