When to use
This name is loaded only when an existing caller specifies the old name; this adapter does not apply to general new requests.
This name is retained for old calls. The sole rule owner is stitch-design-spec; new tasks should use the new entry directly.
Workflow
Step 1: Save the handoff input
Preserve the user request, PRD/existing specification, page/flow ID, framework, design system evidence, edit target, and delivery location; do not expand the user scope.
Step 2: Load the unified entry
Load the installed stitch-design-spec, passing the original input and the output intent:spec-only: requirements/PRD→page specification; continue compiling only when the user also requests prompts. spec-only is the specification-trimmed view of the complete contract and does not require generating prompts first.
Step 3: Return the result
The new entry executes its current rules; return the artifacts, assumptions, verification results, and unfinished items as-is. Forwarding itself does not equal delivery completion.
Step 4: Recovery from missing dependency
If the new entry 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 an old copy of the rules.
Rules and boundaries of non-applicability
Do not collect credentials, and do not send keys or irrelevant account information downstream. This adapter does not apply to directly executing remote generation.
Validation
This entry does not call Stitch, does not require authentication, and does not create pages, systems, or screens on its own. An existing DESIGN.md cannot be upgraded to remote application evidence. Examples, old 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 old name receives “generate page specification only,” pass spec-only; when it receives “only change the search box,” pass the local edit target and do not expand it to a full set of pages. The recovery method for a missing dependency is to explain the missing item and wait for the user to install it or use an already available entry, without silently calling remote tools.
Gotchas
- The old name is a discovery entry, not a Python/CLI/MCP tool; do not treat the skill name as a remote tool call.
- When the user provides both the old name and a complete design specification, pass the specification directly to avoid re-deriving and changing the original page ID.
- When downstream returns partial results or items pending confirmation, the compatibility entry preserves these states and must not rewrite them as “all completed.”
- 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 contains Apache-2.0 content from Google LLC and contributors, which has been migrated into stitch-design-spec; the original license is retained in LICENSE.txt. Upstream pinned snapshot is a community source and is not an officially supported product.