Loading...
Loading...
Found 37 Skills
[Utilities] ⚡⚡⚡⚡ Bootstrap a new project automatically
Learn unfamiliar implementation patterns and fill in missing pieces when building features in a specific environment (e.g., data fetching in a particular runtime). Use when you need to discover or confirm patterns for an unimplemented area; implementation uses erudita and osgrep.
Prepare release documentation including CHANGELOG entry, announcement text, and validation. Run before tagging a new release.
Update existing app design document based on codebase changes and project evolution
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`.
Use this skill when > Design review session that stress-tests plans against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallize. Use when validating architecture or plans against a project's language and documented decisions.
Project scaffolding and management for vibe coding. Initializes opinionated documentation structure, tracks features, and keeps agent context updated. Use when: setting up a new project, tracking features, viewing project status, or managing documentation. Works with Claude Code, OpenCode, Codex CLI, and other skills-compatible agents.
When the user wants to create or update their Unreal Engine project context document. Use when the user says 'project context,' 'set up context,' 'UE context,' 'configure project,' or wants to avoid repeating their project setup across UE development tasks. Creates `.agents/ue-project-context.md` that all other UE skills reference. See related skills footer for skills that depend on this context.
Load project context from .claude/ directory at the start of every task. This ensures Gemini CLI has the same coding rules, design decisions, and library constraints as Claude Code.
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.
Interview the user and write a PRD for Ralph in .prd/prd-<feature>.md.