Packs
1 packResults for “context-md”
13 skillsscaffold-context
Generates a CONTEXT.md routing file for a specified project subdirectory, following the canonical anatomy and ensuring it meets size and content constraints.
0
wiki-agents-md
Generates AGENTS.md files for repository folders to provide coding agents with project-specific context including build commands, testing instructions, code style, project structure, and operational boundaries, only where AGENTS.md is missing.
2.7k
grill-with-docs
Runs a structured interview that stress-tests a plan against the project's domain model, sharpens terminology, and updates CONTEXT.md and ADRs inline as decisions are made.
1 · bundle
release-changelog
Generates the stable Galyarder Framework release changelog at releases/vYYYY.MDD.P.md by reading commits, changesets, and merged PR context since the last stable tag.
20
More results
agent-docs
Writes documentation optimized for AI agent consumption, including SKILL.md, README, and API docs, using layered context hierarchies and RAG-friendly formatting.
10
c4-context
Creates C4 context-level system documentation including system descriptions, personas, user journeys, external dependencies, and Mermaid context diagrams.
42.4k
external-context
Invoke parallel document-specialist agents for external web searches and documentation lookup
1
agents-md
Creates and maintains a minimal, high-signal AGENTS.md file for AI coding agents, covering package manager, file-scoped commands, commit attribution, and key conventions.
2
design-md
Generates a DESIGN.md file conforming to the Stitch (Google Labs) design.md alpha spec, auto-discovering design tokens and components, then emitting YAML frontmatter and eight standard markdown sections.
0
create-agentsmd
Generates a comprehensive AGENTS.md file at the repository root to provide AI coding agents with project context, setup commands, development workflows, testing instructions, and code style guidelines.
36.2k
maintaining-documentation
Maintains a product repo's canonical docs structure (CLAUDE.md, progress.txt, docs/product+system+design-system, context/) as single source of truth, and keeps the log.md session history separate from the progress.txt state snapshot. Trigger after feature completion, before git push, on architecture changes, at session end, or explicit "update docs"/"sync documentation" requests. Skip for trivial changes (<10 LOC, no logic/schema/UI changes).
3
domain-modeling
Maintains a project's domain vocabulary and records architecturally-significant decisions as they're made — a CONTEXT.md glossary and gated ADRs, not passive documentation read once. Use when terminology conflicts or turns fuzzy, when making a decision that's hard to reverse/surprising/a real trade-off, or when a stated domain rule doesn't match what the code actually does.
3
slide-outline
Use this skill whenever a user wants to create a presentation outline, slide deck structure, storyboard slides, or plan a deck for any context (talk, boardroom, email report). Also use when the user mentions "help me structure my presentation", "slide outline", "storyboard my deck", "presentation flow", "plan my slides", "key message for my deck", "pyramid principle for slides", "what slides should I include", or "help me tell a story with slides". This skill walks through a complete, interactive process in two phases: Phase 1 (setup → key message → storyboard) saves a slide-outline.md; Phase 2 (interactive per-slide copy drafting → polish) saves a slide-copy.md that is linked from slide-outline.md. Trigger even when the user only mentions a vague intent like "I need to present X to my team" or "help me put together a board deck".
88 · bundle