HeyEddi-comHeyEddi-com/heyeddi-skills/skills/heyeddi-intake/SKILL.md

heyeddi-intake

Skill0 starsChanged 3 months agoMITView on GitHub

Translates vague user prompts into HeyEddi product docs (personas, route intent, voice), route-specific handoff artifacts (wireframes, user mockups, or briefs), and skill-routing under .heyeddi/. Use first on new projects before @heyeddi-design, @heyeddi-handoff, or @flutter-engineering. Never hand-write product.md: use write_product.

In this repository51 other files it gives its agents.
- .cursor/rules/skill-authoring.mdcCursor rule
- backend-type-bridgerSkill
- composable-patternsSkill
- dart-type-bridgerSkill
- design-handoff-flutterSkill
- design-system-generalizerSkill
- engineering-excellenceSkill
- flutter-engineeringSkill
- flutter-patternsSkill
- heyeddi-designSkill
- heyeddi-handoffSkill
- heyeddi-intakeSkill
- heyeddi-orchestratorSkill
- heyeddi-productSkill
- heyeddi-pr-respondSkill
- heyeddi-pr-reviewSkill
- no-duplicate-uiSkill
- pre-merge-gateSkill
- primevue-openprops-architectSkill
- project-engineeringSkill
- ux-flow-auditorSkill
- verify-buildSkill
- visual-auditorSkill
- backend-type-bridgerSkill
- composable-patternsSkill
- dart-type-bridgerSkill
- design-handoff-flutterSkill
- design-system-generalizerSkill
- engineering-excellenceSkill
- flutter-engineeringSkill
- flutter-patternsSkill
- heyeddi-ci-configSkill
- heyeddi-ci-failsSkill
- heyeddi-ci-guideSkill
- heyeddi-ci-runnersSkill
- heyeddi-designSkill
- heyeddi-handoffSkill
- heyeddi-orchestratorSkill
- heyeddi-productSkill
- heyeddi-pr-respondSkill
- heyeddi-pr-reviewSkill
- heyeddi-setupSkill
- heyeddiSkill
- no-duplicate-uiSkill
- pre-merge-gateSkill
- primevue-openprops-architectSkill
- project-engineeringSkill
- taste-penpotSkill
- ux-flow-auditorSkill
- verify-buildSkill
- visual-auditorSkill

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 1 is distinctive, and 6 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Before any @heyeddi-design / @heyeddi-handoff / scaffold work
line 24
Very specific:
verify_intake --check: must pass before you stop
line 49
Very specific:
Delete src/App.vue or break npm run build to pass verify
line 56
Very specific:
Use write_routing unless overriding build_routing output
line 57
Very specific:
Read reference/clarify-before-act.md.
line 75
Distinctive:
When you have finished the user's request for this skill (not after every tool call or subagent phase), suggest what to run next:
line 79
Very specific:
Add --route /path if you worked a specific route.
line 87

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

HeyEddi Intake

Upstream intake agent: turns vague user language into .heyeddi/product.md, handoff artifacts, and skill routing for downstream HeyEddi skills.

You are not the implementer. You interpret, document, produce handoff artifacts, route, and verify.

When to use

New project or empty / thin .heyeddi/product.md
User describes an app in plain language
User attached images → ingest_mockups (screenshots, sketches, competitor refs)
No images → generate_wireframe per handoff route (default)
Before any @heyeddi-design / @heyeddi-handoff / scaffold work

Mockup decision tree

Read reference/mockup-strategy.md (mandatory).

Situation	Action
User gave screenshots / mockups	`ingest_mockups` → tailor `mockup-brief.md` to their layout
No images, route needs handoff	`generate_wireframe` → refine `wireframe.md` for this product → `seed_brief --force`
No images, polished PNG handoff needed	`prepare_mockup_prompts` → AI-generate `desktop.png` / `mobile.png` (see `reference/ai-mockup-images.md`) → `seed_brief --force`
No images, route needs visual design first	Route `@heyeddi-design`: do not emit template PNGs

The skill package does not ship sample PNGs and has no Pillow/template PNG drawer. Eval hub tooling (uv run poe mockups) is maintainer-only: not part of this skill.

Mandatory pipeline

See reference/pipeline.md. Summary:

load_intake
Draft product-translation.json (reference/audience-intake.md): template: reference/product-translation.template.json
write_product --json … --force: validates schema; writes product.md + saves JSON
write_translation
Handoff features: generate_wireframe (or ingest_mockups / AI PNGs per strategy) → seed_brief --force
build_routing --write --save-input
verify_intake --check: must pass before you stop

Never

Hand-write product.md (missing personas breaks @heyeddi-design)
Skip verify_intake
Implement Vue/Flutter/FastAPI features in this skill (baseline src/App.vue shell on scaffolded repos is OK)
Delete src/App.vue or break npm run build to pass verify
Use write_routing unless overriding build_routing output
Bundle or draw cookie-cutter PNG mockups from skill scripts

Outputs (`.heyeddi/`)

Path	Tool
`docs/intake/product-translation.json`	`write_product` (canonical)
`product.md`	`write_product`
`docs/intake/translation-*.md`	`write_translation`
`docs/intake/skill-routing.json`	`build_routing --write`
`designs/<feature>/wireframe.md`	`generate_wireframe` (default without user images)
`designs/<feature>/mockup-prompts.json`	`prepare_mockup_prompts` (before AI image gen)
`designs/<feature>/desktop.png`	`ingest_mockups` or agent AI image gen after prompts
`designs/<feature>/mockup-brief.md`	`seed_brief` (Audience + Implementation spec)

Clarify before act

Read reference/clarify-before-act.md. One round if personas/competitors missing from user prompt.

When the task is complete: suggest next skills

When you have finished the user's request for this skill (not after every tool call or subagent phase), suggest what to run next:

Run:

python .agents/skills/heyeddi/scripts/suggest_next_skill.py --current-skill heyeddi-intake --project-root .

Add --route /path if you worked a specific route.

Include the script's ### Next step block in your final reply. The user copies the Prompt line into chat (e.g. @heyeddi-design craft /settings).

Pass --mode shape (or craft, audit, etc.) when you know which sub-command just finished.

See @heyeddi → reference/next-skill-handoff.md.

reference/audience-intake.md: JSON schema
reference/downstream-routing.md: routing examples
reference/mockup-strategy.md: when wireframe vs ingest vs AI PNG
reference/ai-mockup-images.md: AI generation workflow (no bundled PNGs)
reference/mockup-quality.md: quality bar per format
@heyeddi: write_skills_index after intake (integration eval)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free