Loading...
Loading...
Found 736 Skills
Onboard a new repository or a repository with scattered documents into the CodeStable system. Two paths are automatically determined: the empty repository path (no spec-type documents or codestable/ directory in the repository) builds the skeleton from scratch; the migration path (the repository already has scattered documents or partial codestable/ structure) first generates an audit report + migration mapping plan, which is finalized after user confirmation one by one. This skill only does two things: "build the skeleton" and "organize existing documents". Once the skeleton is built, all sub-workflows can run directly. Trigger scenarios: Users say "Use CodeStable in this project", "Build CodeStable structure", "Initialize CodeStable", "Migrate to CodeStable".
PRD/Requirement Document Anti-Omission Assistant. When a user provides a requirement document (PRD, functional specification, product document, etc.) and requests to generate front-end pages, implement functions, or carry out development, this Skill must be used first to convert the requirement document into a structured Checklist, then implement code module by module to prevent function omissions. Trigger scenarios: The user sends a .md/.docx/.pdf requirement document and asks you to "generate pages", "implement functions", "write code", "develop this system"; the user says "develop according to this PRD", "generate based on the requirement document", "implement this document"; the user provides a requirement description of more than 200 lines. Even if the user does not mention the checklist, this process should be automatically triggered if the input is a long requirement document (>200 lines) and the goal is to generate code.
Audit and rewrite AI-generated or AI-edited prose to match Ane's IPPF/UNFPA publication standard. Use when the user pastes text and asks to "humanize", "de-AI", "fix the voice", "remove AI slop", "sharpen this", "tighten", "edit for tone", or "review this draft". Strips hedging, filler, nominalisations, em-dashes, passive voice, and abstract openings. Preserves MEL/SRHR register. Does not push prose toward casual or blog tone.
Startup diagnostic router. Use FIRST when a founder doesn't know where to start, has multiple overlapping problems, or asks a vague question like 'what's wrong with my startup', 'why aren't people buying', 'what should I focus on', 'where do I even begin', 'nothing is working'. Routes to the right framework from the 14 available skills — or tells you when no framework fits and you just need to go talk to people. This is the entry point. Use it before reaching for any specific skill.
Helps engineering managers break down knowledge silos and build sustainable documentation and collaboration practices — produces a four-root-cause diagnostic for silos, an Engineering Guilds framework, a minimum-viable documentation approach using ADRs, a structured onboarding model, and a cross-team request decision framework. Use when the user says "knowledge silos," "reinventing the wheel," "nobody reads docs," "onboarding is bad," "teams don't talk," "documentation culture," "cross-team friction," "information doesn't flow," or "new hires struggle to ramp up."
Helps engineering managers plan roadmaps, prioritize work, and communicate priorities effectively — produces the 20% tech debt framework (and its 5 traps), a phased release pressure-test, a maintenance cost model, the Always Green delivery method, sprint anti-patterns, hidden costs of custom features, a critical deadline playbook, the Iron Law of Projects with reference-class forecasting, a "no technical projects" framing, and feature factory warning signs. Use when the user says "roadmap," "quarterly planning," "OKRs," "prioritization," "what should we work on," "planning cycle," "backlog grooming," "stakeholder alignment," "capacity planning," "technical debt," "we're always late," or "leadership doesn't understand engineering work."
One sentence - what this skill does and when to invoke it
Customer.io CLI — use for Customer.io, Journeys, or CDP Pipelines tasks, including getting started phrases like "I want to build with Customer.io", onboarding, signup, sending a first email, campaigns, broadcasts, segments, people, environments, billing, pricing, plans, signing secrets, sources, destinations, track/identify events, `sa_live_` tokens, and `fly.customer.io` / `cdp.customer.io` errors, even when the user does not name the CLI.
Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends/sentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Triggers — "research [topic]", "look into [topic]", "what do we know about [topic]", "investigate [topic]", "find me information on [topic]", "do some research on [topic]", "I need to understand [topic]", or any research request that doesn't obviously match a more-specific specialist skill. Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.
Day 2 (Tuesday) move of a Design Sprint that structures lightning demos and the four-step independent solution sketch protocol (Notes, Ideas, Crazy 8s, Solution Sketch). Each team member produces one solution sketch individually; the skill orchestrates the day but does not author the sketches themselves. Use Tuesday morning after Monday's target moment is locked. Output is the lightning demo board, sketch assignments, and the cohort of independent sketches that become Wednesday's heat-map material.
cuOpt REST server — what it does and how requests flow. Domain concepts; no deploy or client code.
Gain wisdom from setbacks — Go through the 5-step interactive reflection (Setback → Automatic Output → Old Weights → New Parameters → Alternative Action), move from "emotional review" to "behavioral training", and update the L3 weights of your first reactions. Use when Wang Jianshuo reflects on a personal setback, mistake, or recurring pattern (reflection, post-mortem review, review, draw lessons, learn from a setback, gain wisdom, "I messed up again", "Why does this keep happening?", "Why do I always…?", "I can't just let it go", "I know the principles but can't put them into practice"). For the user as a human, not for Claude's task post-mortems.