ChristopherAlphonse
- 57 skills
- 0 followers
- 1 repo stars
- yesterday last updated
- ▌ Lets Talk About It · christopheralphonse bundleOne-pass interrogation and coding guardrails. Use to stress-test a plan, design, code change, or domain term against local code/docs while enforcing explicit assumptions, simplicity, surgical edits, and verifiable success criteria. Also guides a longer feature discussion and turns the settled feature into a copy-ready prompt for a separate implementation session with a chosen sub-agent model roster. Use to explore, narrow, summarize, or hand off a substantial feature without implementing it.
- ▌ Architecture Review · christopheralphonseArchitecture and distributed-systems review that identifies unnecessary complexity, scalability bottlenecks, reliability risks, and infrastructure cost-saving opportunities. Recommends the simplest, most cost-effective architecture based on evidence, with findings marked VERIFIED, [ASSUMPTION], or [NEEDS MEASUREMENT]. Read-only by default, no fixes. Use when: "review architecture", "distributed systems audit", "simplify my architecture", "make this scalable", "reduce infrastructure costs", "find bottlenecks", "architecture review", "/architecture-review"
- ▌ Performance Review Humanizer · christopheralphonseRewrite first-person performance reviews and self-assessments to sound natural, warm, and genuinely human. Preserve every fact, accomplishment, metric, and critical feedback while improving voice, flow, and clarity. Avoid corporate jargon, AI-sounding language, exaggeration, and generic reflections. Can use a sample write-up as a style reference without copying it.
- ▌ Simplify · christopheralphonse bundleRestate the last message in plain human language, with no jargon. Use when the user says they don't follow, or asks to "simplify", "ELI5", "say that plainly", "in plain English", or "what does that mean".
- ▌ QA Review · christopheralphonse bundleRun an extremely strict maintainability review of the author's own changes: abstraction quality, giant files, and spaghetti-condition growth. Use for a deep code quality audit, a strict QA review, or a harsh maintainability review of a diff or PR. Never reviews code the author did not touch.
- ▌ Demo Script · christopheralphonse bundleWrite a short, natural, spoken demo script for a product or feature that explains what changed, shows it working, and ties it to business value. Use for demo scripts, sprint demos, feature walkthroughs, show-and-tell, or explaining a change to stakeholders.
- ▌ Test Review · christopheralphonse bundleJudge whether a diff is adequately tested, for code review. Runs focused sub-agents one after another (regression, behavior and edge cases, concurrency and race conditions, mutation) and reports findings with proof. Reads and runs, never edits the repo. Use for "review the tests", "are these tests good", "is this tested enough", "mutation test this", "test review", or as the test pass of a PR review.
- ▌ Comment Sicko · christopheralphonseA deranged comment-hater that savors deletion and condemns workaround code.
- ▌ Factory Review · christopheralphonse bundleRun a code review through the review and QA skills in this repo as a staged workflow, with a kanban board, a scripted state machine, and a headless tick. Point it at a branch or diff and it scopes the change, runs independent reviewers in parallel, reconciles them into one ranked list, verifies every finding by rerunning the evidence, and writes a report with paste-ready comments. Picks skills for the codebase automatically (TypeScript and React get typescript-strict-style and vercel-react-best-practices, C# gets dotnet, Python gets python). Use when the user wants a branch, PR, or MR reviewed end to end, a verified review, or a review pipeline. Read-only. Never edits the code under review, commits, pushes, or posts comments. To build a feature, use factory instead.
- ▌ Prove It Works · christopheralphonse bundleUse after finishing a task and before saying it is done. Checks the real result (run the feature, read the actual value, look at the actual changes) instead of trusting a stand-in such as a status report, a cached copy, or "it compiles." Finishes by writing a UAT document so the user can confirm the solution works for themselves.
- ▌ Reconcile Reviews · christopheralphonse bundleMerge several review documents of the same PR/MR (from different skills, agents, or people) into one ranked fix list with file and line numbers, then optionally post it to the MR as inline comments. Use when the user has multiple review outputs and asks which claims are most concerning, where they agree or differ, what actually needs fixing and on which line, or to comment the findings on the MR. Not for producing a first review of a diff.
- ▌ Swe · christopheralphonse bundledev mode: the smallest change that fully solves the task, and a reply a busy human understands in one read.
- ▌ Spike · christopheralphonse bundleRun throwaway experiments, sized in story points, to answer a feasibility question before committing to a real build. Use when the user says 'spike this', 'is this even possible?', 'let me try X', 'quick prototype', 'proof of concept', 'compare A vs B', 'before I commit to Y', or 'what should I spike next?'. Not for questions answerable by reading docs or code, and not for production implementation.
- ▌ Dotnet · christopheralphonse bundleIndex and router for C#/.NET work. Use for ASP.NET Core Web API work (adding or changing controller or minimal API endpoints, OpenAPI/Swagger, DTOs, error handling middleware, .http files) and for design pattern reviews of C#/.NET code (Command, Factory, Repository, Provider, DI, SOLID). Picks the one sub-skill that fits and loads it on demand; nothing under this directory is read until a task needs it.
- ▌ Python · christopheralphonse bundleIndex and router for Python work. Use for any Python task: asyncio and concurrency, background jobs and task queues, code style and linting, configuration and settings, design patterns, error handling, observability (logging, metrics, tracing), packaging and publishing, profiling and performance, project structure, retries and timeouts, resource management, pytest, type hints and mypy/pyright, the uv package manager, and an anti-pattern review checklist. Picks the one sub-skill that fits and loads it on demand; nothing under this directory is read until a task needs it.
- ▌ Unslop · christopheralphonseCut AI tells from any writing. Use when drafting or editing prose, replies, docs, PR bodies, or reviews, or when the user says "unslop", "sound less like AI", or "plain English".
- ▌ Factory · christopheralphonse bundleTake a feature from idea to a reviewed local commit by chaining the other skills in this repo as stages (shape, spec, build, review, polish, prove, ship), with a kanban board, a scripted state machine, and a headless tick. Picks skills for the codebase automatically (TypeScript and React get typescript-strict-style and vercel-react-best-practices, C# gets dotnet, Python gets python). Built and measured for Claude Code. Use when the user wants a whole feature driven end to end, a software factory, a pipeline, or the board. Never commits without the user's click and never pushes or opens a PR or MR. To review an existing branch, use factory-review instead.
- ▌ AWS · christopheralphonse bundleIndex and router for AWS work. Use for any AWS task (services, CLI/SDK, infrastructure as code, IAM, networking, storage, databases, compute, containers, serverless, messaging, CI/CD, security, observability, billing, Bedrock/SageMaker, Cognito auth, getting AWS credentials, migrating an app to AWS). Picks the one sub-skill that fits and loads it on demand; nothing under this directory is read until a task needs it.
- ▌ Codebase Exploration · christopheralphonseI am a new developer onboarding onto this codebase. I want to explore it through its primary use cases first. Explore this repository and identify the most common, essential, and core use cases.
- ▌ Documentation Writer · christopheralphonseDiátaxis Documentation Expert with brand voice guidance. An expert technical writer specializing in creating high-quality software documentation, guided by the Diátaxis framework and product copy principles.
- ▌ Systems Architecture · christopheralphonseGenerates a high-level system architecture document by analyzing lifecycle documentation and identifying major actors, their interactions, and technologies used.
- ▌ Task Generation Mode · christopheralphonseGenerates tasks by analyzing the PRD and breaking it into actionable work items.
- ▌ Plan Ceo Opportunities · christopheralphonseSurfaces product expansion, reduction, trust, and positioning opportunities one decision at a time.
- ▌ Plan Review Performance · christopheralphonseReviews performance, scaling, caching, database access, and resource usage risks in a plan.
- ▌ Typescript Strict Style · christopheralphonseEnforces a strict TS/JS coding discipline prioritized as safety, performance, and developer experience. Use when writing/reviewing TS/JS for assertion discipline, exhaustive error handling, function-size and naming conventions, batching/performance design, or dependency minimalism.
- ▌ Plan Review Architecture · christopheralphonseReviews architecture, data flow, dependencies, security boundaries, rollout, and failure scenarios.
- ▌ Plan Review Code Quality · christopheralphonseReviews code organization, maintainability, local patterns, error handling, and diagram freshness.
- ▌ Typescript React Reviewer · christopheralphonse bundleExpert code reviewer for TypeScript + React 19 applications. Use when reviewing React code, identifying anti-patterns, evaluating state management, or assessing code maintainability. Triggers: code review requests, PR reviews, React architecture evaluation, identifying code smells, TypeScript type safety checks, useEffect abuse detection, state management review.
- ▌
- ▌
- ▌ Vercel React Best Practices · christopheralphonse bundleReact and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
- ▌ Csp Bypass Advanced · christopheralphonseAdvanced Content Security Policy bypass techniques. Use when XSS or data exfiltration is blocked by CSP and you need to find policy weaknesses, trusted endpoint abuse, nonce leakage, or exfiltration channels that CSP cannot block.
- ▌ Plan · christopheralphonseStrategic planning and architecture assistant focused on thoughtful analysis before implementation. Helps developers understand codebases, clarify requirements, and develop scoped implementation strategies.
- ▌ QA Only · christopheralphonseReport-only QA testing. Systematically tests a web application and produces a structured report with health score, screenshots, and repro steps — but never fixes anything. Use when asked to "just report bugs", "qa report only", or "test but don't fix". For the full test-fix-verify loop, use /qa instead. Proactively suggest when the user wants a bug report without any code changes.
- ▌
- ▌ Golang Pro · christopheralphonse bundleImplements concurrent Go patterns using goroutines and channels, designs and builds microservices with gRPC or REST, optimizes Go application performance with pprof, and enforces idiomatic Go with generics, interfaces, and robust error handling. Use when building Go applications requiring concurrent programming, microservices architecture, or high-performance systems. Invoke for goroutines, channels, Go generics, gRPC integration, CLI tools, benchmarks, or table-driven testing.
- ▌ Startup Ceo · christopheralphonseUnified founder-mode product review. Orchestrates intake, interrogation, scope mapping, strategy selection, opportunity surfacing, and artifact writing. Delegates parallel research to sub-agents. Keeps user in control of every scope change.
- ▌ Plan Research · christopheralphonseResearch how to implement a phase or planning topic before detailed planning. Produces RESEARCH.md for downstream plan and review skills.
- ▌ Pr Body Style · christopheralphonseDraft or update GitHub pull request bodies in the user's preferred style. Use when an agent writes, rewrites, reviews, or updates a PR description/body, especially when the user asks whether the PR body is accurate, too technical, too long, business-focused, or ready for reviewers.
- ▌ Interrogate Me · christopheralphonse bundleOne-pass interrogation and coding guardrails. Use to stress-test a plan, design, code change, or domain term against local code/docs while enforcing explicit assumptions, simplicity, surgical edits, and verifiable success criteria.
- ▌ Owasp Security · christopheralphonseImplement secure coding practices following OWASP Top 10. Use when preventing security vulnerabilities, implementing authentication, securing APIs, or conducting security reviews. Triggers on OWASP, security, XSS, SQL injection, CSRF, authentication security, secure coding, vulnerability.
- ▌ Playwright CLI · christopheralphonse bundleAutomate browser interactions, test web pages and work with Playwright tests.
- ▌ Whats Going On · christopheralphonseOne-pass codebase intelligence sweep. Use when onboarding to a repo or asking "what's going on here?" Produces a concise map of core use cases, lifecycle, architecture, and where to start reading.
- ▌ Plan Ceo Review · christopheralphonseFounder-mode product review. Rethinks the problem, challenges scope, searches for stronger product opportunities, and chooses one of four review modes: SCOPE EXPANSION, SELECTIVE EXPANSION, HOLD SCOPE, or SCOPE REDUCTION.
- ▌ Plan Ceo Wrapup · christopheralphonseWrites the founder/product review artifact under .planning/reviews and optional strategy doc under .planning/strategy.
- ▌ Plan Eng Review · christopheralphonseEngineering-manager plan review. Locks in architecture, data flow, edge cases, tests, performance, rollout, and failure handling before implementation. Uses smaller local review skills for each review pass.
- ▌ Security Review · christopheralphonse bundleUse this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides scoped security checklist and patterns.
- ▌ Frontend Patterns · christopheralphonseFrontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.
- ▌ Plan Ceo Strategy · christopheralphonseSelects founder-mode review posture and challenges product strategy before execution.
- ▌ Plan Review Scope · christopheralphonseChallenges implementation scope before detailed engineering review.
- ▌ Plan Review Tests · christopheralphonseProduces a test diagram, identifies coverage gaps, and writes a .planning QA handoff artifact.
- ▌ Process Task List · christopheralphonseGuidelines for managing task lists in markdown files to track progress on completing a PRD
- ▌ Jest React Testing · christopheralphonse bundleComprehensive React component testing with Jest and React Testing Library covering configuration, mocking strategies, async testing patterns, hooks testing, and integration testing best practices
- ▌ Plan Review Intake · christopheralphonseFinds review inputs for plan review workflows using only local project files under .planning.
- ▌ Plan Review Wrapup · christopheralphonseSynthesizes plan review sections into a .planning review artifact and readiness summary.
- ▌ Root Cause Analysis · christopheralphonse bundleConduct systematic root cause analysis to identify underlying problems. Use structured methodologies to prevent recurring issues and drive improvements.
- ▌ Code Review Frontend · christopheralphonse bundleMulti-agent PR review orchestrator. Discovers codebase quality standards first (lint, format, build, CI), then spawns specialized agents in parallel to surface real issues in the git diff. Agents report findings only — no fixes. Every finding is VERIFIED or tagged [ASSUMPTION]. Use when: "review this PR", "code review", "check my diff", "/review"