Loading...
Loading...
Found 58 Skills
Structured workflow for implementing new features with planning, clarification, and documentation. Use when implementing new features, making significant changes, or when the user requests a feature that requires planning and multiple implementation steps. Triggers on feature requests, multi-step implementations, or when explicit planning is beneficial.
guidelines for creating, reviewing, updating, and searching ADK documentation - use when users ask about writing, maintaining, or auditing ADK bot docs
Readme.com integration. Manage Projects. Use when the user wants to interact with Readme.com data.
Merges valuable content into permanent documentation, then deletes source files. Use when you have untracked *_REPORT.md or *_ANALYSIS.md files, git status shows markdown artifacts that shouldn't be committed, preparing PR and need to clean up working artifacts, preserving insights from code reviews. Do not use when files are already in docs/ or skills/ locations. DO NOT use when: files are intentionally temporary scratch notes. DO NOT use when: source files have no extractable value.
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.
Bootstrap a repo for the strict development workflow: discover issue tracker, triage labels, and docs layout, then write docs/agents/*.
Guides developers and admins through direct interaction with the Fusion Help REST API — reading articles, FAQs, release notes, searching content, and managing help documentation programmatically. USE FOR: fetch help articles from API, integrate help content in app, search help content, manage help documentation via API, automate help content, build help tooling. DO NOT USE FOR: using the fhelp CLI tool (use fusion-help-docs skill), modifying Fusion.Services.Help backend code, or non-help-API tasks.
Maintain organized project documentation with metadata headers. Update existing docs before creating new ones. Use when writing or editing any project documentation.
End-of-session knowledge cleanup with OCD-level rigor — reconciles project docs (CLAUDE.md, README.md, docs/) and agent memory against the code so nothing rots. OCD-level review and synchronization of project documents and agent memory after a session. MUST trigger when the user says: "sync up", "tidy up docs", "update memory", "clean up docs", "/sync", "/neat", "sync up", "tidy up docs", "tidy up", "update memory", "organize", "wrap up", "this phase is done", "newcomers can start directly", or any phrase suggesting a development milestone where knowledge needs reconciliation. Also trigger when the user reports stale docs, conflicting memories, or wants a clean handoff to teammates or other agents. A standalone "tidy" with prior development context counts — do not under-trigger. Cross-platform: works on Claude Code, OpenAI Codex, OpenCode, and OpenClaw.
steering skill Trigger terms: steering, project memory, codebase analysis, auto-update context, generate steering, architecture patterns, tech stack analysis, project structure, analyze codebase, understand project Use when: User requests involve steering tasks.
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.
Turn ideas into fully formed designs and specs through natural collaborative dialogue. Use when planning new features, designing architecture, or making significant changes to the codebase.