Vadim Flowed
34 lines
1.3 KiB
Markdown
34 lines
1.3 KiB
Markdown
# Prompt Guidelines
|
|
|
|
Use these guidelines when drafting prompts for the four wireframe skills.
|
|
|
|
- Put the role, goal, inputs, output contract, and quality gates near the top.
|
|
- Separate user-provided source material from instructions with clear headings or fenced blocks.
|
|
- Ask for structured JSON when downstream tools depend on exact keys.
|
|
- Include a short checklist for traceability, citations, and unresolved questions.
|
|
- Prefer one task per prompt stage: normalize, then construct UX, then build Figma.
|
|
- Do not ask the model to hide uncertainty. Preserve contradictions and missing decisions.
|
|
- Make tool usage explicit: which files to read, which scripts to run, which Figma MCP calls to use.
|
|
- Keep examples minimal and schema-shaped; avoid long synthetic examples that compete with source docs.
|
|
- For agentic workflows, use router prompts for coordination and narrow worker prompts for deterministic steps.
|
|
- Treat UX research claims as citations, not decoration. If a source does not support the decision, do not cite it.
|
|
|
|
## Prompt Skeleton
|
|
|
|
```text
|
|
Role: <specialized skill>
|
|
Goal: <one workflow step>
|
|
Inputs:
|
|
- <artifact paths>
|
|
- <source constraints>
|
|
Output:
|
|
- <exact artifact paths and schema keys>
|
|
Quality gates:
|
|
- <validation checks>
|
|
- <traceability/citation checks>
|
|
Process:
|
|
1. Inspect inputs.
|
|
2. Produce the artifact.
|
|
3. Validate and list open questions.
|
|
```
|