Loading...
Loading...
Found 2,893 Skills
Story decision capture and mining — recording what was decided, what was rejected, and why, inline with the artifacts they relate to. Use whenever story direction is being chosen, brainstorm options are being narrowed, character or world choices are being made, or past decisions need to be recovered from session history.
Use after run-plan completes to independently verify the implementation. Reads only the plan document and inspects the codebase from scratch — information-isolated from the execution context. Produces a structured review document with PASS/FAIL verdict. Triggers when the user says "review the work", "verify the implementation", "check if the plan was executed correctly".
Turn git commits and diffs since an exact start date into a copy-pastable, non-technical client report grouped by feature. Use when the user wants a client update, accomplishment summary, weekly progress note, stakeholder recap, or high-level status report based on git history. Trigger on: client report from commits, summarize git diff since a date, weekly update from git log, non-technical accomplishments, stakeholder-ready changelog. Do NOT trigger for technical release notes, code review, or any request where the date is still ambiguous.
Customize Rspress themes using CSS variables, Layout slots, component wrapping, or component ejection. Use when a user wants to change the look and feel of an Rspress site, override theme components, add custom navigation/sidebar/footer content, inject global providers, or modify the default Rspress theme in any way. Also use when a user mentions theme/index.tsx, Layout slots, BEM class overrides, or rspress eject.
Creates agent-optimized technical design documents with context-layer-aware progressive disclosure for architecture decisions, component design, and data models. Use when writing technical designs, architecture docs, defining system components, or making technology choices for spec-driven development.
Guides users through documenting business flows step-by-step in EventCatalog. Use when user asks to "document a flow", "map a business process", "create a flow diagram", "walk through a process", "document an end-to-end flow", or "map out how something works in my architecture".
Manages the ai-context/ memory layer: initialize from scratch, update with session work, or maintain/cleanup. Trigger: /memory-init, /memory-update, /memory-maintain, initialize memory, update memory, maintain memory.
港股K线数据查询。获取日线、周线、月线行情。 当用户询问"腾讯日K""港股K线""港交所周线""恒指月线"时触发。
Conduct a targeted code exploration of the repository, and document the process of "Ask Questions → Read Code → Draw Conclusions" as searchable evidence for direct reuse when similar questions arise next time. There are three types: question (investigate code around a specific question and provide conclusions), module-overview (sort out the structure, boundaries, entry points, and dependencies of a module), and spike (conduct lightweight technical exploration of multiple possible directions without making final decisions). Trigger scenarios: Users say "Let's explore first", "How is X implemented in this repository", "Quickly get familiar with this module", "Archive the exploration results". Refer to `codestable/reference/system-overview.md` for how to distinguish it from learning / tricks / decisions.
Initialize a new repository with AGENTS.md
Extract canonical domain terms into CONTEXT.md. Flag ambiguities (same word, different meanings) and synonyms (different words, same meaning). Re-invoking updates the file in place. Use when authoring or updating CONTEXT.md, or when a new domain term emerges in conversation.
Documents the results of a time-boxed technical or design exploration (spike). Use after completing a spike to capture learnings, findings, and recommendations for the team.