article-prompts-to-skills

Article Prompts to Skills

Turn source prompts into small, demonstrable capability packages. Preserve the useful behavior, not the source page's brand or layout.

1. Inspect Before Extracting

1. Read the repository instructions and the complete source article.
2. Run git status --short; preserve unrelated work.
3. Inventory every explicit prompt, heading, example, asset, and acceptance criterion.
4. Search existing SKILL.md files for overlapping capabilities before creating folders.
5. If the source is raw HTML and the prompts do not exist yet, use $html-to-interaction-prompts first, then return here.

Do not infer a family of skills from a title alone. Trace each proposed skill to source evidence.

2. Build an Extraction Ledger

Create a working table before editing files:

Source prompt	Reusable capability	Keep	Remove	Skill name	Demo proof

Apply these boundaries:

• Create one skill per independently reusable behavior.
• Merge steps only when separating them would make either step unusable.
• Update an existing skill when its contract already covers the capability.
• Skip decorative or editorial fragments that do not create a repeatable method.
• Name skills after the outcome or mechanism, never after the source article.

3. Extract the Portable Contract

Keep the source's successful mechanics:

• behavior and state transitions;
• data model and parameter defaults;
• timing, easing, spacing, and responsive rules;
• accessibility, reduced-motion, and keyboard behavior;
• performance constraints and failure modes;
• acceptance checks that prove the result.

Remove source-specific packaging:

• brand names, marketing copy, and proprietary content;
• page layout that is unrelated to the capability;
• hard-coded palettes, assets, and selectors;
• incidental implementation choices that do not affect the outcome.

The result must transfer to a different subject, layout, and visual system without rewriting the core instructions.