Claude Skills by matteocervelli

Design system architecture, API contracts, and data flows. Use when translating analyzed requirements into technical design for feature implementation.

Implement features with code, tests, and documentation. Use when building features from approved designs following TDD and project coding standards.

Validate code quality, test coverage, performance, and security. Use when verifying implemented features meet all standards and requirements before marking complete.

Analyze feature requirements, dependencies, and security considerations.

Design REST APIs or function contracts with clear request/response specifications,

Generate CHANGELOG entries following conventional commits format with

Review code for quality, security, and performance with comprehensive

Analyze test coverage with detailed metrics, identify gaps, and generate

Analyze project dependencies, build dependency trees, detect conflicts,

Update all project documentation including implementation docs, user

Generate Jest-based unit tests for JavaScript/TypeScript code. Creates

Verify compliance with OWASP Top 10 2021 security standards. Use when

Permission test. Use for testing.

Generate project assessment markdown documents from JSON data with WHY/WHO/WHAT

Create comprehensive pull requests with detailed descriptions, test plans,

Safely merge GitHub pull requests using comprehensive pre-merge validation. Use this skill when the user asks to merge a PR, complete a PR workflow, or check if a PR is ready to merge. Validates CI/CD status, reviews, and conflicts before merging with the appropriate strategy.

Auto-activates when generating Product Requirements Prompt (PRP) documents

Generate pytest-based unit tests for Python code. Creates test files

Validate Python code quality with formatting, type checking, linting,

Auto-activates when managing agent-to-agent communication for validation

Auto-activates when analyzing GitHub issues to extract functional requirements,

Validate Rust code quality with rustfmt, clippy, cargo check, and security

Auto-activates during requirements analysis to assess security risks

Scan codebase for security vulnerabilities including secrets, insecure

Auto-activates during requirements analysis to evaluate technical stack

Execute test suites with proper configuration, parallel execution, and

Generate test scaffolding for modules with proper structure, fixtures,

Validate TypeScript/JavaScript code quality with ESLint, Prettier, type

Generate comprehensive unit tests with proper structure, mocking, and

Auto-activates when coordinating sequential validation specialists with

Check version compatibility, breaking changes, and security vulnerabilities

Assess identified vulnerabilities for exploitability, impact, and risk.

Bypass attempt. Use for security testing.

Create distinctive, production-grade frontends by composing design dimensions and tech-specific implementations

Plan sprints with capacity management, dependency checking, and priority-based story selection

Validate user stories against INVEST criteria and suggest improvements

Add technical context, implementation hints, and effort estimates to user stories

Create user stories from feature descriptions with interactive Q&A and automated validation

Run SQL queries against psql, BigQuery, or MySQL from the terminal, including natural-language-to-SQL and schema exploration. Use when analyzing data, inspecting DB state, or debugging tables. Trigger on "query the database", "SQL", "show me data from", "explore table".

Fetch Claude Code documentation and help update configuration. Use /claude-code-guide <topic> where topic is: memory, skills, hooks, agents, settings, mcp, plugins, cli, overview, all

Claude-native review of code for quality, structure, naming, and maintainability (no external AI). Use when reviewing a file or diff for code quality before committing. Trigger on "review this code", "code review", "is this well-written". For security, use /security-verify; for companion-AI review, use /review.

Post-merge deployment workflow covering feature flags, canary/blue-green rollout, smoke-test verification, and rollback triggers. Use after a PR is merged and you need to ship it safely to production. Trigger on "deploy", "roll out", "canary", "feature flag", "rollback".

Audit dependency freshness — scan outdated deps and CVEs, classify severity, record update/defer/skip decisions in Atrium, gate PASS/WARN/FAIL. Use when checking for outdated packages or deciding whether to upgrade. Trigger on "outdated dependencies", "dependency audit", "are my deps up to date", "should I upgrade".

Investigate bugs with unknown root cause. Spawns fresh-context investigation subagent + parallel /review solve companion, persists hypotheses across iterations, hands off to /fix when root cause found.

Phase 0 validation gate — problem framing, competitive analysis, feasibility, and a go/no-go checkpoint before committing to a feature. Use when evaluating whether an idea is worth building, before /story or /design. Trigger on "is this worth building", "validate this idea", "discovery", "should we build".

Audit Dockerfiles and Compose files against the 10 common Docker mistakes — image security, build efficiency, runtime safety. Use when reviewing or hardening Docker configs. Trigger on "audit my Dockerfile", "check this Compose file", "Docker best practices", "is my container secure".

Build and publish project documentation — Starlight (Astro) for apps, markdown for libraries/services, with IT+EN i18n and VPS deploy. Use when writing user guides, scaffolding a docs site, or publishing docs. Trigger on "write docs", "documentation site", "user guide", "publish docs".

Fix bugs and technical debt with minimal ceremony. Issue GitHub optional — provide one for traceability or work free-form. Replaces /issue-fix.

Design UI, build components, write Playwright E2E tests, run WCAG accessibility audits, and do visual review. Use when building or testing frontend/UI work. Trigger on "build a component", "frontend", "E2E test", "accessibility audit", "a11y", "visual review", "make this look good".

Holistic project audit across endpoints, versions, docs, security, quality, CI, and library dimensions. Use when checking overall project health or running a periodic cross-cutting audit. Trigger on "project health", "audit the project", "health check", "is this project in good shape".