learnprompt-single-mdx
SolidCreate or rewrite exactly one LearnPrompt Starlight MDX tutorial to the repository's golden-sample standard, with bottom-of-page auditable sources instead of SourceCard, a research pack, evidence ledger, reproducible showcase, independent review, quality score, and successful site build. Use for one LearnPrompt article, tutorial, chapter, or MDX page; in batch goals, invoke once per topic in an isolated task.
Install
Quality Score: 82/100
Skill Content
Details
- Author
- LearnPrompt
- Repository
- LearnPrompt/LearnPrompt
- Created
- 3 years ago
- Last Updated
- yesterday
- Language
- MDX
- License
- NOASSERTION
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
write-prompt-guide
Produce a pack-specific PROMPT_GUIDE.md that teaches end users what to type to get a good run out of one Agent Skill pack, from that pack's own SKILL.md, README, and open issues. Use when a skill pack has agent-facing docs but nothing telling a human how to invoke it well.
meta-prompt
Use when the user wants help writing, generating, or improving a prompt for an LLM - e.g. "write me a prompt for...", "turn this into a prompt", "help me prompt for...", "improve this prompt", or when they hand over a use case and want a polished, reusable prompt back. Produces a finished, copy-ready prompt (not advice about prompting). Also applies when the user references the CoSTAR framework or asks for a prompt built to a named structure.
prompt-master
Compile a raw idea (feature, refactor, migration, bug hunt, research) into a sequenced pack of copy-paste-ready prompts for Opus/Sonnet-class models — one prompt per development phase (research → spec → plan → implement → verify), each self-contained, grounded in the project's real facts, and chained through artifact files so the methodology survives fresh sessions and less self-driving models. TRIGGER when: the user wants prompts to run later or elsewhere ("generate prompts for this idea", "prompt pack", "how would I drive Opus/Sonnet through this", "разложи идею на промпты"), or wants a phased prompt plan instead of doing the work now; ALSO when the input is a whole surface rather than one change ("audit this whole area", "review every screen", "map all of X and tell me what to fix") — that is the program pass, and it is authored here, not by /prepare. DO NOT TRIGGER when: the user wants the work done in THIS session (route via /which-skill or run the pipeline skills directly), wants a spec (/analyst), a pl