Loading...
Loading...
Found 26 Skills
Post-implementation cleanup of correct code. Prunes comments aggressively: deletes what restates the code, files design rationale to the commit message and wider context to the PR or an issue, collapses one mechanism explained in three places, strips issue and PR references that make a file unreadable on its own, compacts genuine gotchas, renames unclear symbols so a comment is not needed, checks the code against the project's conventions, and simplifies what is more complicated than it needs to be. Tightens docs without gutting them. Auto-applies and reports.
Scaffold new modules and components for pplx-sdk following the layered architecture and established code patterns.
Project-wide coding standards and conventions specialist. Use PROACTIVELY when writing code, making architectural decisions, or establishing project conventions. Covers coding style, commenting, error handling, validation, tech stack consistency, and project conventions across all languages and frameworks.
Core TypeScript conventions for type safety, inference, and clean code. Use when writing TypeScript, reviewing TypeScript code, creating interfaces/types, or when the user asks about TypeScript patterns, conventions, or best practices.
Analyze existing repositories, maintain structure, setup guardrails and best practices
Statistical rule discovery through measurement of Go codebases: Count patterns, derive confidence-scored rules, produce Style Vector fingerprint. Use when analyzing codebase conventions, extracting implicit coding rules, profiling a repo before onboarding or PR automation. Use for "analyze codebase", "find coding patterns", "what conventions does this repo use", "extract rules", or "codebase DNA". Do NOT use for code review, bug fixes, refactoring, or performance optimization.
Makes Flutter code changes match the existing project and reuse existing widgets, services, helpers, styles, assets, and conventions. Use whenever writing or modifying Flutter code, or when flagging duplicate components and inconsistent patterns during a review. Governs style and consistency of edits; does not itself authorize making edits — respect the calling task's mode.
Use when scaffolding a new repository (public or private) to the Patina Project baseline, when realigning an existing repository with that baseline, or when auditing or adding commit conventions, PR templates, husky + commitlint, PNPM tooling, release-please, agent docs (AGENTS.md, CLAUDE.md), or AI agent plugin manifests for Claude Code, Codex, Cursor, Windsurf, and Copilot. Triggers on phrases like "scaffold this repo", "scaffold a Patina plugin", "realign with the baseline", "audit our repo conventions", "set up commitlint and husky", or "add Codex/Cursor/Windsurf surfaces".
Achra Platform guidelines, business rules, architecture, and engineering patterns. Use when writing or refactoring Achra code, adding modules or components, creating or updating skeleton loaders, loading placeholders, Suspense fallbacks, or Next.js loading.tsx, answering questions about Achra architecture or business domains, deciding when to use feature flags, applying Achra naming and placement conventions, or answering which technologies and libraries the project uses.
Rules and guidelines for working with Spring Data JPA in the project. ALWAYS use this skill when adding, removing, or modifying JPA entities, repositories, or projections. Trigger on any request that involves changing entity structure, adding new entities, modifying field annotations, updating database mappings, creating or modifying Spring Data repositories, or defining query projections (interfaces, DTOs).
Java coding standards for Spring Boot and Quarkus services: naming, immutability, Optional usage, streams, exceptions, generics, CDI, reactive patterns, and project layout. Automatically applies framework-specific conventions.
Implement the requested changes. Write production-ready code, follow existing patterns, and run tests to verify your work.