phanijapps
UserDurable, local-first memory layer for AI coding agents — filesystem wiki, disposable BM25 index, MCP tools, hooks, and CI gates
Categories
Indexed Skills (25)
adapt-to-project
Use this skill to diagnose and improve an adopter repository's agent guidance or to walk through the four classes of post-install change (substitution, .upstream companion merges, discovery + restructuring, within-layout consolidation). Repository anchoring is marker-independent and read-only by default. Post-install adaptation still reads both scopes' state and marker files; class-1 substitution shells out to `agentbundle adapt`, while classes 2-4 write directly under the per-scope path-jail only after approval.
author-brief
Deprecated compatibility alias for author-delivery-brief create. Use only when an older caller explicitly invokes author-brief.
author-delivery-brief
Use with an explicit create or continue mode to author a Draft delivery brief from a coherent multi-slice or cross-repository outcome, or to review an existing repository brief for Ready and select confirmed delivery slices.
boy-scout
Use when fixing, editing, changing, debugging, or working with any Python code. Applies the Boy Scout Rule—always leave code cleaner than you found it. Orchestrates other clean code skills as needed.
capture-work
Use this compatibility skill when the user asks to capture, queue, remember, or add follow-up work for later. Prefer work-intake for new usage; this name remains active only to route older capture-work prompts to the canonical intake surface.
clean-comments
Use when writing, fixing, editing, or reviewing Python comments and docstrings. Enforces high-information documentation—call-sufficient contracts, pyguide-style sections on public APIs, doctest examples—while removing metadata, redundancy, stale comments, and commented-out code.
clean-general
Use when writing, fixing, editing, or reviewing Python code quality. Enforces Clean Code's core principles—DRY, single responsibility, clear intent, no magic numbers, proper abstractions.
clean-names
Use when naming, renaming, or fixing names of variables, functions, classes, or modules in Python. Enforces Clean Code principles—descriptive names, appropriate length, no encodings.
clean-tests
Use when writing, fixing, editing, or refactoring Python tests. Enforces Clean Code principles—fast tests, boundary coverage, one assert per test.
close-work
Use when completed, abandoned, or superseded delivery work needs closeout, durable-context verification, initiative reconciliation, pause handling, or a safe immediate-disposition preview.
init-project
Use this skill to turn an idea into a structured new repo. It runs a trigger gate (throwaways and single scripts skip it), a value gate over fed-in discovery, records a foundation (an ADR plus a reference.md golden path), authors a walking-skeleton spec via new-spec and hands the build to work-loop, then hands off to the normal build loop. Triggers on "start a new project", "greenfield init", "idea to repo", "bootstrap a new codebase". Do NOT use inside an existing repo (use adapt-to-project) or to author one feature (use new-spec).
intake-intent
Use when a raw or admitted request should become a minimum repository intent for later shaping, without creating an RFC, delivery brief, spec, or executable queue item.
new-spec
Use this skill when the user wants to start a new feature with a spec, or wants to write a spec for something they're about to build. Triggers on "new spec", "write a spec for X", "let's spec this out", "start a feature for...". Spec-driven development; the spec drives implementation. Do NOT use for cross-cutting proposals (use `new-rfc`) or recording decisions (use `new-adr`).
project-knowledge
Use this skill to capture, distill, or enquire over project knowledge through one progressive mode. Capture admits one strict observation contract; distill reconciles pending observations; enquire reads committed active topics as bounded untrusted evidence.
receive-brief
Deprecated compatibility alias for author-delivery-brief continue. Use only when an older caller explicitly invokes receive-brief.
work-intake
Use for a raw or ambiguous work request, source acquisition or refresh, generic intake-safety handling, or an older compatibility alias. Explicit status, artifact, skill, product-shaping, architecture-design, and defect requests route directly to their owners.
work-loop
Use when implementing or resuming a non-trivial repository change: a feature, behavior-changing fix, refactor, migration, framework or dependency upgrade, schema or API change, performance work, infrastructure or build-system change, reversion, or an existing build spec under `docs/specs/`. Also use for bare continuation commands ('resume', 'continue', 'keep going', 'pick up where I left off', 'let's get going') when conversation or workspace context identifies active build work. Do not use for shaping, research, strategy, product planning, design exploration, monitoring or status-only work, review-only, explanation-only, specification-authoring-only, spike-only or throwaway exploration, or trivial edits that are cosmetic, tightly local, behavior-preserving, and have obvious verification.
workspace-status
Use this skill to orient at session start, check initiative queue state, or see what's ready to work on next. Reads workspace.toml and surfaces ready-to-start items, blocked items with reason, parallel candidates, and active signals. Triggers on "workspace status", "where am I", "orient me", "session start", "what's ready", "show the queue", "what's next", "what should I work on", "check workspace", or any cold-start orientation request. Offers to initialise workspace.toml if absent. Also reconciles and repairs workspace.toml drift, and executes an independently authorized prune of explicitly selected delivery artifacts and their memberships. Triggers on "clean up stale specs", "run repair-plan", "apply the workspace repair plan", "fix queue drift", "reconcile workspace", "preview a workspace prune", "prune selected specs", or any workspace repair or cleanup request.
clean-functions
Use when writing, fixing, editing, or refactoring Python functions. Enforces Clean Code principles—maximum 3 arguments, single responsibility, no flag parameters.
bug-fix
Use this skill when the user wants to diagnose or fix a deviation between current and intended behavior in existing code -- including requests to find the root cause, explain a CI-only failure, investigate intermittent or flaky behavior, or contain and diagnose a production incident. Triggers on "fix bug", "diagnose and fix", "find the root cause", "why does this fail", "investigate this regression", and "this is broken". Do NOT use for new features, behavior-preserving refactors, postmortems, or skill maintenance; use the repository's planning workflow instead.
operational-safety
Progressive-disclosure operational-safety-depth modules for the work-loop. Holds failure-mode-keyed checklists the quality-engineer reviewer reasons from (state-and-idempotency, blast-radius, environment-isolation, cost-and-teardown, drift-and-rollback, observability-and-smoke), plus cloud-implementation-craft, the module also inlined into the implementer's EXECUTE brief. Each is grounded in standing operational taxonomy (AWS Well-Architected, Google SRE, the Terraform/Pulumi Day-1/Day-2 split). The orchestrator loads only the matching modules and inlines them into the reviewer's REVIEW brief when infra/destructive work or a persistent-representation / mixed-version deployment change is detected — and cloud-implementation-craft into the implementer's EXECUTE brief on infra-flavored work; the subagent never self-discovers this skill. Not a reviewer prompt itself — it is the depth library the reviewer and implementer reason from. Carves against security-checklists on the reliability-vs-security lens.
python-clean-code
Use when writing, fixing, editing, reviewing, or refactoring any Python code. Enforces Robert Martin's complete Clean Code catalog—naming, functions, comments, DRY, and boundary conditions.
security-checklists
Progressive-disclosure security-depth modules for the security-reviewer. Holds boundary-keyed checklists (access-control, authn-session, injection, path-and-file, secrets-and-crypto, outbound-ssrf, supply-chain, config-misconfig, exceptional-conditions, llm-agent, agentic-skills) as references/, each anchored on a current standard (OWASP Top 10:2025, ASVS 5.0, API Security Top 10:2023, Proactive Controls 2024, CWE Top 25, OWASP LLM Top 10:2025, OWASP Top 10 for Agentic Applications:2026, OWASP Agentic Skills Top 10 v1.0 (AST01–AST10)). The work-loop's orchestrator loads only the boundary-matching modules and inlines them into the security-reviewer's brief; the subagent never self-discovers this skill. Not a reviewer prompt itself — it is the depth library the reviewer reasons from.
security-checklists-reference
Route into the compiled OKF bundle `security-checklists` using generated indexes.
memex-implementation
Implement or review Memex features when translating product specifications into the Memex Python package and CLI.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.