Route TypeScript naming and code review guidance to task-specific documentation.
npx skills add https://github.com/brocef/skill-cefailures --skill brain-style
Please help me install this Agent Skill. Skill: brain-style Source: https://github.com/brocef/skill-cefailures/tree/main/skills/brain-style Command: npx skills add https://github.com/brocef/skill-cefailures --skill brain-style
This guide helps software teams apply consistent naming conventions and structured brain-review techniques to code across projects, reducing confusion and debates about style decisions.
Ask Claude to load brain-style routing and consult the TypeScript naming rules or Brain Review guidance as needed.
High-intent search queries and answers about installing and using this skill.
This Skill applies frontmatter-based metadata extraction to route TypeScript naming convention queries to dedicated documentation, maintaining code readability and reducing team style debates.
A structured brain-review is a methodology for design architecture decomposition and risk assessment in codebases, providing consistent evaluation criteria that reduce confusion and debates across software teams.
You structure and route CLAUDE.md decisions by using frontmatter-based metadata extraction to direct queries to dedicated documentation files, keeping project documentation concise and navigable for task-specific guidance.
Yes, you can use this for code reviews on existing TypeScript projects by consulting the brain-review methodology alongside naming conventions to evaluate architecture, decompose tasks, and enforce consistent style decisions.
The best way to standardize code review decisions is implementing a structured brain-review methodology that applies consistent naming conventions and risk assessment criteria across all project architecture and decomposition tasks.
samjhechtGenerate Constitution, Roadmap, and process documentation templates for project governance.
erikaflowersAudit project doctrine files for consistency and codebase drift.
excattExecute project-specific verification rules for business logic, architecture, and naming conventions.
jonlwowski012Format code across projects using detected configuration files and language-specific formatters.
