Loading...
Loading...
Found 43 Skills
A skill with an orphan reference file. Do NOT use for real work.
Collaborative design exploration for new features and architecture decisions. Triggers: 'brainstorm', 'ideate', 'explore options', or /ideate. Presents 2-3 approaches with trade-offs, documents chosen approach. Do NOT use for implementation planning or code review. Requires no existing design document — use /plan if one exists.
Document business rules, technical patterns, and service interfaces discovered during analysis or implementation. Use when you find reusable patterns, external integrations, domain-specific rules, or API contracts. Always check existing documentation before creating new files. Handles deduplication and proper categorization.
Conduct targeted code exploration on a repository, and document the process of "Asking Questions → Reading Code → Reaching Conclusions" as searchable evidence for direct reuse when similar questions arise next time. There are three types: question (investigate code around a specific problem and provide conclusions), module-overview (organize the structure, boundaries, entry points, and dependencies of a module), spike (conduct lightweight technical exploration of multiple possible directions without making final decisions). Trigger scenarios: When users say "Let's explore first", "How is X implemented in this repository", "Quickly get familiar with this module", "Archive the exploration results". For the distinction from learning / tricks / decisions, refer to the root skill `easysdd`.
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`.
guidelines for creating, reviewing, updating, and searching ADK documentation - use when users ask about writing, maintaining, or auditing ADK bot docs
Applies targeted improvements to an existing pm-skills skill based on feedback, validation reports, or convention changes. Reads current files, previews proposed changes, writes on confirmation, and suggests a version bump. Use when improving a skill after validation or feedback.
Create a new Architecture Decision Record with sequential numbering and AgentDB registration
Create advanced animations with Principle - design interactive prototypes with complex motion and transitions
Interview the user and write a PRD for Ralph in .prd/prd-<feature>.md.
Readme.com integration. Manage Projects. Use when the user wants to interact with Readme.com data.
Onboard a new repository or a repository with scattered documents into the easysdd system. Two paths are automatically determined: the empty repository path (no spec-like documents or easysdd/ directory in the repository) builds the skeleton from scratch; the migration path (the repository already has scattered documents or partial easysdd/ structure) first generates an audit report + migration mapping plan, which is confirmed by the user one by one before implementation. This skill only does two things: "build the skeleton" and "organize existing documents". After the skeleton is built, all sub-workflows can run directly. Trigger scenarios: the user says "Use easysdd in this project", "Build easysdd structure", "Initialize easysdd", "Migrate to easysdd".