mwillbanks
- 14 skills
- 0 followers
- 6 hours ago last updated
- ▌ Code Discipline · mwillbanks bundlePrevent trivial helpers, wrapper layers, rename-only utilities, duplicate constants, and local reinvention. Enforce reuse of platform primitives, framework capabilities, shared utilities, and proven libraries. Use when adding or reviewing helper sprawl, object-vs-positional parameter decisions, arrow-vs-declaration choices, class-vs-functional design, god-file boundaries, schema-file boundaries, security/maintainability hardening, or UI structure so the agent keeps code disciplined and avoids technical debt.
- ▌ Project Tracker · mwillbanks bundleCoordinate ticket tracking and time tracking before, during, and after implementation work. Use whenever a prompt starts with `/ProjectTracker`, includes Jira keys like `AIA-123`, includes ClickUp custom IDs like `SL-7007`, or asks to sync work across parent and child boards while logging time.
- ▌ Github Pr Review · mwillbanks bundleReview GitHub pull requests directly in GitHub using GitHub MCP or gh, leave precise inline comments and final review states, and apply hard-nosed scrutiny for security, architecture, maintainability, testing, accessibility, and frontend compliance. Use whenever the user asks to review a PR, inspect a GitHub pull request, request changes, re-review a PR, post inline review comments, or submit a GitHub review instead of a local-only code review.
- ▌ Biome Enforcement · mwillbanks bundleUse this skill when a task touches code, tests, Biome config, or generated artifacts and Biome must remain the final remediation and enforcement pass using the required JSON changed-files command.
- ▌ Agent Execution Mode · mwillbanks bundleParent-agent execution policy for implementation, validation, delegation, and mandatory code review orchestration through the code_review_ts sidecar.
- ▌ Cloud Native Runtime · mwillbanks bundleUse when implementing, reviewing, or hardening cloud-native backend/runtime work: APIs, Lambda/serverless functions, background workers, Pulumi or IaC, EventBridge or scheduled jobs, S3/object-storage file uploads, media processing, CloudFront/CDN, networking, caching, secrets, observability, production deployment, architecture review, resilience, or cloud-service equivalency. Do not use for UI-only React/CSS/design/copywriting/blog/README-only tasks unless they change runtime, infrastructure, deployment, security, or observability behavior.
- ▌ Spec Change Governance · mwillbanks bundleGovern spec amendments without losing history, completed work, or review context. Use when the user wants to change requirements, amend a plan, update a spec in place, mark superseded items, rerun clarification or planning, or prevent spec drift during rework.
- ▌ Review Remediation Gate · mwillbanks bundleClose review findings deterministically, remediate blocking issues, and prove review closure. Use when the user says to fix review comments, address review findings, run a review-remediation pass, close out blockers, or finish work only after review issues are resolved.
- ▌ TS Code Validation Gate · mwillbanks bundleEvaluates completed TypeScript changes before review using a fail-closed evidence gate across formatting/linting, unit tests, semgrep, osv-scanner, and fallow, and blocks new review attempts until prior remediation-ledger items are fully resolved.
- ▌ Execution Alignment Gate · mwillbanks bundleDetects materially ambiguous or under-specified requests, selects the right clarification target, and enforces bounded alignment before execution, including spec-governed continuations and approval-gated manager handoffs. Use when ambiguity could cause wrong deliverables, wrong scope, wrong implementation path, avoidable rework, or token waste from repeated follow-up.
- ▌ Frontend System Discipline · mwillbanks bundlePrevent frontend work from inventing local design tokens, theme constants, helper layers, or style-file sprawl. Use when building or reviewing UI, components, pages, theme tokens, styled files, composition, or helper placement in frontend code.
- ▌ Repo Standards Enforcement · mwillbanksUse this skill to enforce repository-wide standards for toolchain compliance, package-manager purity, type safety, testing, maintainability, and architecture. When a more specific skill exists for a concern such as final linting or formatting remediation, that more specific skill takes precedence over this skill's generalized guidance.
- ▌ Speckit Feature Orchestrator · mwillbanks bundleOrchestrates a full Speckit feature workflow from constitution amendment through specification, clarification, plan, tasks, and analysis as a chief-architect governor using subagents. Use when the repository already uses Speckit or the user explicitly asks for Speckit and wants to discuss, refine, or directly drive a new feature into implementation-ready Speckit artifacts in one controlled pass.
- ▌ Requirements Traceability Matrix · mwillbanks bundleBuild a requirements-to-implementation trace matrix that proves coverage and exposes gaps. Use when the user asks to trace requirements, map specs to code, prove coverage, identify missing validation, or build a matrix for review, planning, or compliance work.