Loading...
Loading...
Found 1,951 Skills
Organize reusable programming patterns, library usages, and technical techniques that address "This is the correct way to do such tasks" into a prescriptive reference library, which can be retrieved and reused on demand during feature-design and issue-analyze phases. There are three types: pattern (design patterns, programming idioms), library (usage and pitfalls of a specific library/framework), technique (specific operation skills / command recipes). Trigger scenarios: when users say "Record a trick", "This usage is worth noting", "tricks", "Record library usage", or when valuable techniques worth documenting and archiving are discovered during feature-design / issue-analyze phases and actively pushed. For how to distinguish it from learning / decisions / explore, refer to the root skill of `easysdd`.
Transform a feature description into a structured spec.md
Generates a full comprehensive status update of the project. Use when the user asks for a status update, progress report, "STATUS UPDATE", "WHAT'S THE STATUS", or wants to know what's done, what's broken, and what's next. Writes to docs/status/.
Create consistent, formatted README files for zenon-red repositories. Use when writing or updating README.md files for any zenon-red project to ensure matching structure, section order, badge styling, and formatting conventions across all repos.
Mandatory unless the user explicitly opts out. Use when non-trivial work on features, bug fixes, refactorings, or changes to code, tests, configuration, dependencies, runtime assets, or design requires explicit planning before implementation.
Create/refresh lean repo memory docs and root AGENTS.md guidance for handoffs, stale status, next steps, or post-work capture.
Draft concise morning meeting notes summarizing overnight developments, trade ideas, and key events for coverage stocks. Designed for the 7am morning meeting format — tight, opinionated, actionable. Triggers on "morning note", "morning meeting", "what happened overnight", "trade idea", "morning call prep", or "daily note".
Establish durable brand and voice context for cross-skill consumption. Generates BRAND.md (audience, positioning, do/don't editorial rules, taboo phrases, competitor differentiation) and VOICE.md (existing persona JSON re-expressed as readable prose), both written to the project root. When present, all blog sub-skills auto-load these files before writing or reviewing. Pairs with blog-persona, which manages the structured persona JSON. Use when user says "blog brand", "create brand context", "brand voice doc", "BRAND.md", "VOICE.md", "establish editorial brand", "brand guidelines for blog".
This skill should be used when the user asks to "create a README", "generate a README", "make a readme", "write a README for my project", "need a README", "add a README", "document my project", "set up project docs", "readme with badges".
Add a new effect to @remotion/effects, including implementation, package exports, docs, demos, preview images, tests, formatting, and builds.
Design a new PM skill through guided conversation. Use when you have raw content or an idea and want to shape it into a compliant skill.
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.