Loading...
Loading...
Found 46 Skills
Update the project README.md with comprehensive documentation based on the current codebase state. Use when the README needs updating or is outdated.
Guide writing a structured initiative brief for roadmap-first planned work in One Horizon. Use when asked to "write an initiative", "draft an initiative brief", "plan this initiative", "turn this idea into an initiative", or "help me scope this roadmap work". This skill produces a design doc, not code. Requires One Horizon MCP.
Create or update structured daily entries in docs/devlog.md under <!-- DEVLOG_ANCHOR -->. Supports APPEND and CHANGE modes. Only edits docs/devlog.md. No code execution, no dependencies, no secrets.
Full Lifecycle Management of Issue Pool (Development Paradigm v1 Planning Phase). The core is an issue-driven process: users throw in ideas casually, and you turn vague issues into actionable tasks—what you deliver is "problem definition", not "solution implementation"; the carrier is a single markdown file named ISSUES.md at the root of the repository, without introducing kanban or new formats. Five actions: Record (add original content to the pool + relevance check), Merge (merge homogeneous requirements), Break Down (discuss and decompose, guide users to reveal the real needs behind the proposed solutions), Transfer (deliver outputs), Pending (if the issue is still vague after two rounds of discussion, record the bottlenecks and put it back into the pool, and avoid making fake plans to wrap up). The only criterion for judging during Transfer is "whether it can be delivered in one version": If yes → simple task, write a paragraph plus 3~5 acceptance criteria under the pool entry; If no → complex plan, place it in docs/plan/ and write the framework plan content following the seven steps in references/plan-writing.md (explain "why to do it / what constitutes completion / what steps to take", without involving fields or interfaces), the end must remain vague, and break down the next batch only after delivering one batch. When users say "record an issue", "add/summarize issues", "break down an issue / decompose"
Create ASCII diagrams for markdown using graph-easy. TRIGGERS - ASCII diagram, graph-easy, architecture diagram, markdown diagram.
Manage a consumer repo's Prelude docs viewer content — prelude.docs.pages, groups, mdSplit README hero, and generated nixosOptions pages. Use when adding or fixing project documentation shown by `docs` / `x docs`, wiring the README landing page, or generating option docs.
This skill should be used when the user asks to "format markdown", "write markdown documentation", "follow markdown style guide", "apply markdown conventions", or needs guidance on markdown best practices.
This skill should be used when the user asks to "create a location", "add a location", "magic system", "political system", "build the world", "add culture", "world history", "technology system", "religion", "economy", or wants to develop any aspect of a story's world and setting.
Validate ASCII diagram alignment in markdown. TRIGGERS - diagram alignment, ASCII art, box-drawing diagrams.
Installs a live docs.page site from a public GitHub repository by following Quickstart. Use when the user wants to add docs.page, install docs.page, scaffold docs.json, or host markdown documentation at docs.page/{owner}/{repo}.
When the user wants to create or update their startup context document. Also use when the user mentions "set up context", "tell you about my startup", or any other skill needs context that doesn't exist yet.
Break a PRD into independently-workable issues and write each as a local markdown file in issues/. Use when the user wants to turn a PRD into a list of concrete tasks.