virajp
UserPlugins for Claude Code
Categories
Indexed Skills (75)
analysis-options
Opinionated analysis_options.yaml for Flutter — extends flutter_lints with an explicit strict linter rule set, the formatter block (page_width 120, automate trailing commas), analyzer error severities, and generated-code excludes. The concrete backing of the dart skill's style rules; a clean `flutter analyze` is the merge gate. Auto-applies when editing analysis_options.yaml.
dart
Flutter & Dart development — the always-on coding baseline plus deep references for state management, architecture, navigation, UI/theming/animation, performance, data & networking, Firebase, media, monetization, native interop, and build tooling. Auto-applies when editing any Dart file. Use when writing or reviewing any Flutter/Dart code; read the reference matching your task.
internationalization
How the Flutter app localizes — ARB files with English as the template, l10n.yaml config, the genarb → arb_translate → gen-l10n pipeline, GetMaterialApp delegate wiring, and L10n.of(context) usage. Auto-applies when editing ARB files or l10n.yaml.
kotlin
Writing the Android-native (Kotlin) side of a Flutter app for features Flutter can't reach — a MethodChannel handler registry, main-looper dispatch, notImplemented defaults, and Native↔Flutter invocation. Auto-applies when editing any Kotlin file.
pubspec
Opinionated pubspec.yaml standards for Flutter apps — unconstrained versions pinned by the lock file, a pub.dev URL comment per package, dependencies vs dev_dependencies, SDK constraints, and code-gen packages. Auto-applies when editing pubspec.yaml or pubspec.lock.
documentation-standards
Opinionated standards for writing and maintaining Markdown documentation — writing style, code blocks, tables, CHANGELOGs, and diagrams. Auto-applies when editing any Markdown file.
readme
Create or update the repository's README — scan the codebase and document it with a title, short description, a project list, an architecture mermaid diagram with notes, an infrastructure (cloud tools) section, a local development setup guide, per-project sections (monorepo or polyrepo), and the important task-runner commands. Follows the documentation-standards skill.
mise
Opinionated mise configuration — the .config/ three-file split (mise.toml / mise.dev.toml / mise.ci.toml) selected by MISE_ENV, the shared settings block, runtime-vs-dev-vs-ci tool placement, the env-value split, the CI node-gpg workaround, and the mandatory file-based task library (init,_scripts/_helpers, code/*, setup/*). Auto-applies when editing any mise config or task file.
scaffold
Scaffold the mise three-file split (mise.toml / mise.dev.toml / mise.ci.toml) plus the mandatory task library (init, _scripts/_helpers, code/*, setup/*) into a repo's .config/, detecting the language runtime.
lint-format
The house lint/format gate — @askviraj/linter (ESLint, bundled) as the lint gate and dprint as the formatter. Both must pass before commit. Covers how to run each, how to scope rule overrides, and common failure remedies. Auto-applies when editing dprint.json, eslint config, or .config/linter.yaml.
package-json
Opinionated package.json standards for single-package repos and pnpm monorepos — pnpm as the only package manager, "latest" versions, ESM, the exports map, the standard build/check/clean/test scripts, and (in a workspace) workspace:* links. Auto-applies when editing any package.json.
pnpm
Opinionated pnpm configuration for single-package repos and monorepos — pnpm-workspace.yaml as pnpm's settings file (supply-chain safety via minimumReleaseAge/trustPolicy, build allowlists, overrides, peer-dependency rules, .npmrc) plus the monorepo layout (package globs, workspace linking, catalogs, requiredScripts). Auto-applies when editing pnpm-workspace.yaml or .npmrc.
tsconfig
Opinionated TypeScript config layout for single-package repos and pnpm monorepos — a strict shared tsconfig.base.json, per-project tsconfig.json with the @/ path alias, a tsconfig.build.json emit variant, and (in a workspace) project references. Auto-applies when editing any tsconfig file.
architecture
Create or update docs/blueprint/registry.yaml — the machine-readable Project Registry every command parses — and docs/blueprint/architecture.md, its prose system-shape view.
archive
Move completed cycle plans out of the active set into docs/plans/archived/. Never deletes. May be run manually or offered at the end of execute.
blueprint-authoring
Authoring discipline for vwf blueprints — the code-independence line that keeps a blueprint a durable technical contract, plus the per-entity, cross-entity/integration, and UI/UX completeness bars. Auto-applies when editing any docs/blueprint file. Read the reference matching the surface you are pinning down.
blueprint
Maintain the always-current, full-product blueprint under docs/blueprint/ — flow docs as the primary unit, entity data contracts, and per-service OpenAPI contracts, plus conventions.md. Stack-agnostic; resolves section→project mapping from the architecture registry. Gated by fresh subagent completeness reviewers per doc and one whole-product coherence review at the end of the sweep. A run sweeps flow by flow until whole-product coverage holds, then stamps it in .config/vwf.yaml — /vwf:plan halts without a complete stamp.
design-system-authoring
Authoring discipline for a product's design system — the code-independent UX/visual contract (semantic tokens, typography, spacing, motion, accessibility standard, component behaviors, anti-patterns) that every blueprint screen references. Auto-applies when editing docs/blueprint/design-system. Read the reference matching the layer you are defining.
design-system
Import the product's Claude Design design system into docs/blueprint/design-system.md — the product-wide UX/visual contract (semantic tokens, typography, spacing, motion, accessibility standard, component behaviors) every blueprint screen references — and pin design.design_system_id in .config/vwf.yaml. A vwf foundation, mandatory once the product has a UI surface. Design systems are authored and iterated on claude.ai/design; this skill imports, it never authors visual language.
execute
Execute an approved cycle plan end-to-end in a dedicated worktree — dependency-ordered, code then review+security concurrently per step under TDD with finding loops, one E2E acceptance + UX-conformance pass after all steps, gaps captured in the plan doc. Autonomous between the start and one final human gate, which reviews the run and approves the merge. Requires an approved plan in docs/plans/.
feedback
The front door for production feedback — a bug, a metric reading, a UX complaint, or a feature idea. Classifies it and routes it into the doc and command that fix it (gaps → blueprint/plan, metrics → product, UX → design-system/screens). "canvas" harvests the claude.ai/design review conversations across every pinned design project into the same routes. Durable even when mempalace is down.
git-workflow
Manage git workflows �� worktree isolation, commits, merges, and pushes. Use for all substantive changes; never work directly in the main worktree.
handoff
Capture the current session as a handoff document and file it to mempalace (wing=<project>, room=handoff, drawer=<name>) so work can resume in a fresh session. With no argument — or `next` — it writes the reserved `next` handoff, to mempalace and to docs/handoffs/next.md, which /vwf:recall resumes automatically. Use when the context window grows beyond ~60%.
mockups
Render the blueprint's screens as self-contained static HTML mockups — one page per screen plus the state variants the Screens contract pins, styled from design-system tokens — into the repo's gitignored docs/scratchpad/ tree for local browser review. Mockups are realizations, never contract; never pushed to Claude Design, never committed.
plan
Produce reviewable cycle plans as diffs for one slice of the blueprint (a flow or an entity). Reads desired (blueprint) vs actual (code), writes only the delta to docs/plans/<date>-<time>-<slice>.md. Resolves the slice's transitive dependency chain and plans each unimplemented dependency as its own plan doc first, in order; routes any blueprint gap it uncovers back through /vwf:blueprint before writing — so no cycle builds on a gap. Requires the blueprint coverage stamp to read complete.
product
Create or update docs/blueprint/product.md — the problem, target users, success metrics, and slice priority the whole blueprint serves. The Phase −1 foundation; blueprint halts without it.
recall
Retrieve a handoff document from mempalace (wing=<project>, room=handoff, drawer=<name>) to resume work in a fresh session, and optionally run its next prompt. With no argument — or `next` — it resumes the reserved `next` handoff and runs its continuation without asking. Use to continue after a session that exceeded ~60% context.
rest-api-design
Comprehensive, technology-agnostic principles and best practices for designing REST APIs. Use this skill whenever designing new REST endpoints, reviewing API contracts, planning versioning strategy, defining error formats, or establishing API standards for a project. Also trigger when discussing backward compatibility, API security, pagination, rate limiting, authentication schemes, or OpenAPI spec authoring — even if the user doesn't say "REST API" explicitly. This skill is the authoritative guide for all API design decisions.
screens
Two-way screen sync with Claude Design. "prompt <flow>" writes one wireframe-level design brief per platform (docs/prompts/screens/<project>/<NNN>-<flow>/<platform>.md) — always the flow's full screen blueprint, regenerated in place, never a change note, transcribing each screen's contract-pinned components and their rules — commissioning one interactive page per flow per platform on the claude.ai/design canvas under a strict naming contract (pages <flow>--<platform>, frames named by the pinned screen codes, happy paths stitched into index--<platform>); it also maintains each platform canvas project's conventions CLAUDE.md (CLAUDE--<platform>.md — one design project per platform, generated sections regenerated, canvas-owned section preserved); the files are the deliverable, never run against the canvas; "import [flow]" reads the designed pages back as data, diffs them against the Screens contracts (components included), folds canvas-discovered conventions back into the conventions file, and routes every accep
verify
Verify a deployed environment against the blueprint — health-check each deployed project and re-run the flows' acceptance criteria in staging mode. Run after you (or CI) deploy; vwf never deploys. A clean pass against the production environment offers to record a release, freezing each deployed service's API contract into docs/blueprint/apis/released/. Failures route through the feedback machinery.
doctor
Check that the repo actually matches what .config/vwf.yaml declares — per-language LSP servers and toolchains, each project's frameworks and dependencies against its manifest, the harness task names, health endpoints, the mempalace wing and room set, the graphify CLI/graph/hook, and format-stamp drift. Reports; never writes without consent. Run it after setup, before execute, or any time the repo and the config might have drifted apart.
installer-cli
Authoring discipline for the @askviraj/ai-plugins CLI — the read-only receipt path, the interactive uninstall, packaging, and the flag surface. Auto-applies when editing cli/ or tsup.config.ts.
plugin-authoring
Authoring discipline for Claude Code plugins — directory-convention discovery, the invocation frontmatter and the silent failure the wrong state causes, manifest fields and the marketplace traps, and hooks. Auto-applies when editing anything under plugins/. Read the reference matching what you are changing.
claude-code-stack-menu
Return the stack templates the claude-code plugin offers, as a vwf menu payload. Invoked by /vwf:architecture and /vwf:setup when `claude-code` is listed in the config's `stacks:` — not a general-purpose skill.
claude-code-stack-template
Return one claude-code stack template as a vwf template payload — its axis fields, per-capability harness mechanisms, and conventions. Invoked by /vwf:architecture and /vwf:setup after the user picks from the claude-code menu — not a general-purpose skill.
cloudflare-stack-menu
Return the Cloudflare stack templates this plugin offers, as a vwf menu payload. Invoked by /vwf:architecture and /vwf:setup when `cloudflare` is listed in the config's `stacks:` — not a general-purpose skill.
cloudflare-stack-template
Return one Cloudflare stack template as a vwf template payload — its axis fields, per-capability harness mechanisms, and conventions. Invoked by /vwf:architecture and /vwf:setup after the user picks from the cloudflare menu — not a general-purpose skill.
datastore-stack-menu
Return the datastore templates this plugin offers, as a vwf menu payload. Invoked by /vwf:architecture and /vwf:setup when `datastore` is listed in the config's `stacks:` — not a general-purpose skill.
datastore-stack-template
Return one datastore stack template as a vwf template payload — its axis fields, per-capability harness mechanisms, and conventions. Invoked by /vwf:architecture and /vwf:setup after the user picks from the datastore menu — not a general-purpose skill.
design-tools-import-conversations
Read the design review conversation back from a project's design tool (Claude Design, Lovable or Google Stitch) and return it as a vwf conversations payload. Invoked by /vwf:feedback canvas as its design adapter — not a general-purpose skill.
design-tools-import-design-system
Read the design system back from the project's design tool (Claude Design, Lovable or Google Stitch) and return it as a vwf design-system payload. Invoked by /vwf:design-system as its design adapter — not a general-purpose skill.
design-tools-import-screens
Read a flow's designed screens back from the project's design tool (Claude Design, Lovable or Google Stitch) and return them as a vwf screens payload. Invoked by /vwf:screens import as its design adapter — not a general-purpose skill.
devtools-stack-menu
Return the stack templates the devtools plugin offers, as a vwf menu payload. Invoked by /vwf:architecture and /vwf:setup when `devtools` is listed in the config's `stacks:` — not a general-purpose skill.
devtools-stack-template
Return one devtools stack template as a vwf template payload — its axis fields, per-capability harness mechanisms, and conventions. Invoked by /vwf:architecture and /vwf:setup after the user picks from the devtools menu — not a general-purpose skill.
docker
Docker/OCI doctrine — one shared multi-stage Dockerfile per repo, the same digest promoted rather than rebuilt per environment, and Compose as the local stack behind `wait-on` readiness gates (vwf's one non-negotiable harness mechanism). Auto-applies when editing a Dockerfile, a compose file, or .dockerignore.
doppler
Development-time secret injection with Doppler — secrets reach a process as environment variables and are never read from a committed file, `doppler run --` wraps the mise task rather than the application, and nothing here is in the deployed path. Auto-applies when editing doppler config or a mise config that wires it.
dprint
dprint as the repo's single formatter — one root config, plugins pinned by version, `excludes` for generated trees, and the `exec` escape hatch for languages dprint has no plugin for. Formatting authority; correctness belongs to the linter. Auto-applies when editing dprint.json.
eslint
ESLint as the repo's correctness gate — flat config only, zero formatting rules, overrides scoped by `files` glob rather than disabled globally, and one lint command wired through the task library. Auto-applies when editing an eslint config or .config/linter.yaml.
gitleaks
gitleaks as the repo's secret scanner — scan the working tree on every commit and the history once, allowlist by fingerprint rather than by rule, and treat a hit as a credential to rotate rather than a line to silence. Auto-applies when editing .config/gitleaks.toml.
grype
grype as the repo's dependency vulnerability scanner — scan the source tree on every commit and the built image before release, fail on a severity threshold, and time-box every ignore rule. Auto-applies when editing .config/grype.yaml.
pre-commit
pre-commit as the local gate — config at .config/pre-commit-config.yaml, hooks that call mise tasks so the same command runs locally and in CI, revs pinned and updated deliberately, and `files:` scoping so a hook fires only for what it validates. Auto-applies when editing a pre-commit config.
flutter-stack-menu
Return the Flutter stack templates this plugin offers, as a vwf menu payload. Invoked by /vwf:architecture and /vwf:setup when `flutter` is listed in the config's `stacks:` — not a general-purpose skill.
flutter-stack-template
Return one Flutter stack template as a vwf template payload — its axis fields, per-capability harness mechanisms, and conventions. Invoked by /vwf:architecture and /vwf:setup after the user picks from the flutter menu — not a general-purpose skill.
flutter-ux-gate
Run a Flutter UI slice's visual and accessibility checks, returning findings in vwf's UX-gate vocabulary. Invoked by vwf's `execute-ux-reviewer` for a project whose stack this plugin owns — not a general-purpose skill.
gcp-cost
How Google Cloud services actually bill, and the traps that turn a cheap architecture expensive — per-service cost models, the design decisions that move the bill, and the guardrails to put in first. Use when choosing between GCP services, reviewing a design for cost, or diagnosing a bill.
gcp-iam
Least-privilege identity on Google Cloud — the service-account shape per workload, why keyless beats JSON keys, the roles that are quietly over-broad, and how Firebase security rules relate to IAM. Use when wiring service auth, granting access, or reviewing a design for privilege.
gcp-local-stack
Which Google Cloud services can run locally, which cannot, and what to do about the ones that cannot — the emulator map behind vwf's `local_stack` harness capability. Use when setting up local development or E2E tests against a GCP-backed product, or when deciding whether a stack needs Docker.
gcp-stack-menu
Return the Google Cloud stack templates this plugin offers, as a vwf menu payload. Invoked by /vwf:architecture and /vwf:setup when `gcp` is listed in the config's `stacks:` — not a general-purpose skill.
gcp-stack-template
Return one Google Cloud stack template as a vwf template payload — its axis fields, per-capability harness mechanisms, and conventions. Invoked by /vwf:architecture and /vwf:setup after the user picks from the gcp menu — not a general-purpose skill.
identity-stack-menu
Return the identity templates this plugin offers, as a vwf menu payload. Invoked by /vwf:architecture and /vwf:setup when `identity` is listed in the config's `stacks:` — not a general-purpose skill.
identity-stack-template
Return one identity stack template as a vwf template payload — its axis fields, per-capability harness mechanisms, and conventions. Invoked by /vwf:architecture and /vwf:setup after the user picks from the identity menu — not a general-purpose skill.
object-storage-stack-menu
Return the object-storage templates this plugin offers, as a vwf menu payload — deliberately none, with the reason. Invoked by /vwf:architecture and /vwf:setup when `object-storage` is listed in the config's `stacks:` — not a general-purpose skill.
object-storage-stack-template
Return one object-storage stack template as a vwf template payload — this plugin ships none, so every slug is an error naming the cloud plugins that do. Invoked by /vwf:architecture and /vwf:setup after the user picks from the object-storage menu — not a general-purpose skill.
observability-stack-menu
Return the observability templates this plugin offers, as a vwf menu payload. Invoked by /vwf:architecture and /vwf:setup when `observability` is listed in the config's `stacks:` — not a general-purpose skill.
observability-stack-template
Return one observability stack template as a vwf template payload — its axis fields, per-capability harness mechanisms, and conventions. Invoked by /vwf:architecture and /vwf:setup after the user picks from the observability menu — not a general-purpose skill.
orchestration-stack-menu
Return the async-orchestration templates this plugin offers, as a vwf menu payload. Invoked by /vwf:architecture and /vwf:setup when `orchestration` is listed in the config's `stacks:` — not a general-purpose skill.
orchestration-stack-template
Return one async-orchestration stack template as a vwf template payload — its axis fields, per-capability harness mechanisms, and conventions. Invoked by /vwf:architecture and /vwf:setup after the user picks from the orchestration menu — not a general-purpose skill.
stackgen-stack-menu
Return the stack options the stackgen plugin offers — its shipped packs plus the one open entry, generate-for-anything-uncovered — as a vwf menu payload. Invoked by /vwf:architecture and /vwf:setup when `stackgen` is listed in the config's `stacks:` — not a general-purpose skill.
swift
The iOS-native (Swift) side of a Flutter app — the Swift/SwiftUI coding baseline, MethodChannel bridging from AppDelegate, and Xcode project/build workflows. Auto-applies when editing any Swift file. Use when writing native iOS code or working with the Xcode project; read the reference matching your task.
typescript
TypeScript development — the always-on coding baseline plus deep references for Effect-TS patterns, Vitest testing, and the monorepo build pipeline. Auto-applies when editing any TypeScript file. Use when writing or reviewing any TypeScript code; read the reference matching your task.
project-setup
Onboarding and migration discipline for bringing a repo into vwf's format and keeping it current — topology detection, consent-gated dry-run migration, the blueprint format version + drift map, and the CLAUDE.md vwf section. Used by /vwf:setup; trigger when onboarding a repo to vwf or migrating an existing one to the latest blueprint format.
product-foundations
The foundational concerns every product must decide — users & operators, observability, audit logs, change logs, background processes, data retention & PII, notifications, runtime settings, rate limiting, reliability targets, disaster recovery & backup, cost guardrails. Elicited defaults distilled from the 95octane reference implementation. Used by /vwf:architecture (the foundations checklist) and /vwf:blueprint (expanding accepted foundations into contracts); read the reference matching the foundation being decided or expanded.
release
Cut a release of @askviraj/ai-plugins — the i:release ritual, the GitHub Release note format, and the CI facts that make a failed publish legible. Run when the user asks to cut, tag, or publish a release.
stackgen-stack-template
Return one stackgen stack as a vwf template payload — reading the materialized entry from the repo's .claude/ tree, or, on a first pin, resolving the bundle's composition and dispatching per component (shipped pack components copied, uncovered components generated) behind a consent gate. Invoked by /vwf:architecture, /vwf:setup, /vwf:plan and /vwf:execute — not a general-purpose skill.
workflow
Explicit project workflow router. Call this to start any product or engineering work. NOT auto-triggered.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.