Loading...
Loading...
Found 3,211 Skills
A meta-skill for creating/writing custom Skills for the Aike Smart Parking Open Platform CLI (openydt), benchmarked against Feishu's lark-skill-maker. It is used when users want to encapsulate a specific openydt interface or a business process into a reusable Skill, create a new openydt domain Skill, standardize the directory structure and frontmatter of SKILL.md, extract the catalog command list, add --yes to write operations, or learn how to write an openydt Skill. Trigger words: create openydt skill, write an openydt skill, encapsulate openydt interface, create a parking domain skill, openydt skill maker, skill template, SKILL.md specification, how to write frontmatter, how to list command list, turn this interface into a skill, benchmark against lark-skill-maker, parking open platform skill, skill scaffolding, skill directory structure.
English alias for /aprende. Runs the same five-pass workflow to surface reusable learnings from the current conversation across memory, lesson, skill, and project-doc categories — with confirmation before any write. Alias en inglés para /aprende.
Produces a standalone multi-page research dossier on the jackin' docs site from a brief, drawing on web and codebase evidence. Use when the operator runs /jackin-dev:research.
Doctrine Extensions (Gedmo). Use when working with doctrine extensions.
Run /scope to turn a product idea into a living, coarse scope in docs/scope/ and keep it current: plan a new product, plan the next slice, enroll one named feature, or run with no argument to reconcile after shipping and queue what is next. Seeds WHAT to build; /architect designs, /develop builds.
Audit whether a repo's docs actually ANSWER the questions a reader has — by spawning fresh, cheap (Haiku) agents that cold-read ONLY the docs and measuring how fast they reach the answer, whether they hit dead-ends, whether they fall back to source code, and whether they cite docs that contradict each other. Use after a doc reorg, when docs "feel scattered," or when the same confusion keeps recurring. Surfaces findability gaps (a corpus can be COMPLETE — every doc indexed — yet not FINDABLE) plus a prioritized fix list. Works on any repo's docs, not just this one.
Use when working-backwards discovery is complete and you need to synthesize a PRFAQ, FAQ package, and business requirements document tied to business value, scenarios, and testable acceptance logic. Supports `--quick-flow` for fast assumption-driven execution and `--full-flow` for question-driven verified execution. Explicit full or end-to-end spec refinement requests continue through the existing 18-stage refinement cascade.
Creates safe rollback procedures for deployments with automated workflows, rollback runbooks, version management, and incident response. Use for "rollback automation", "deployment recovery", "incident response", or "production rollback".
Creates 4 core project docs (requirements.md, architecture.md, tech_stack.md, patterns_catalog.md). L3 Worker invoked by ln-110-project-docs-coordinator. ALWAYS created.
Write/restructure the "(3) Research Basis" section of the NSFC main text, and simultaneously organize "Working Conditions" and "Research Risk Responses". Use an evidence chain to prove the project is feasible, resource conditions align with research content, and risk contingency plans are executable. Suitable for scenarios where users need to write/revise sections such as "Research Basis, Preliminary Work, Feasibility Analysis, Working Conditions, Platform Team, Risk Responses".
Use when setting up or configuring Storybook for a project. Covers main configuration, addons, builders, and framework-specific setup.
Create advanced animations with Principle - design interactive prototypes with complex motion and transitions