ワンクリックで
assistant-framework
assistant-framework には laimis91 から収集した 16 個の skills があり、リポジトリ単位の職業カバレッジとサイト内 skill 詳細ページを表示します。
このリポジトリの skills
Clarify ambiguous or multi-intent requests. Use when the user asks to untangle, structure, or restate what they mean.
Manage durable memory safely. Use for explicit remember, recall, forget, or memory-health requests and stable corrections or preferences.
Review code and re-review fixes until clean. Use for explicit code review or the workflow Review phase; QA runs only when required.
Create or update V1 skills and contracts. Use for skill scaffolding, contract design, or contract-compliance validation.
Run proportional development phases. Use to plan, build, implement, fix, migrate, or refactor project artifacts.
Generate and rank options. Use light mode for quick improvement scans and deep mode for explicit brainstorming or broad exploration.
Diagnose unknown failures by reproducing and isolating before fixing. Use for debugging, root causes, flaky tests, or unexplained breakage.
Apply Red-Green-Refactor. Use when tests-first/TDD is requested or required by project conventions.
Gather and synthesize source-backed information. Use for explicit research, topic investigation, current evidence, or option comparison.
Reflect on evidence-backed lessons or recall prior ones. Use for explicit retrospectives, calibration, or a concrete durable lesson.
Create or update Telos purpose, mission, goals, challenges, and strategies. Use for explicit purpose or Telos work.
Create Mermaid architecture, sequence, ER, flow, class, or state diagrams. Use for explicit diagram or system-flow visualization requests.
Create or update README, API, architecture, changelog, or migration docs. Use for explicit documentation work.
Map an unfamiliar codebase and its patterns. Use for onboarding, project orientation, or explicit codebase-learning requests.
Analyze threats, vulnerabilities, dependencies, and attack surfaces. Use for explicit security work or changes to auth, input, or sensitive data.
Reason through architecture decisions and complex trade-offs. Use for explicit stress tests, debate, first principles, or hypotheses.