Paul Pessoa
Community@paulpessoa
Frontend Engineer
Agent Skills by Paul Pessoa
Showing 8 vetted skills indexed across 1 GitHub repositories.
modular-decomposition
Analyzes monolith codebases to size components, detect duplication, measure coupling, and group modules into domains.
web-quality-audit
Audits web projects for performance, accessibility, SEO, and best-practice issues with severity-ranked findings.
coupling-analysis
Analyzes module coupling using strength, distance, and volatility dimensions from software architecture theory.
tlc-spec-driven
Plans and implements features through adaptive Specify, Design, Tasks, and Execute phases with deterministic validation scripts.
react-best-practices
Applies 57 Vercel performance rules when writing, reviewing, or refactoring React and Next.js code.
react-composition-patterns
Refactors React components using compound components, lifted state, and context-based composition patterns.
create-adr
Creates Architecture Decision Records in MADR, Nygard, or Y-Statement formats.
frontend-blueprint
Guides structured design discovery before generating frontend UI code.
Frequently Asked Questions About Paul Pessoa
FAQPage SchemaWhat tasks can I accomplish with Paul Pessoa's skill registry?▼
You can decompose monoliths into domain-aligned modules, analyze module coupling, run combined web quality audits covering performance, accessibility, and SEO, apply React/Next.js performance and composition patterns, plan features with EARS requirements and atomic commits, create Architecture Decision Records, and design frontend interfaces through structured discovery.
Who should use these skills?▼
Frontend engineers, React and Next.js developers, software architects evaluating modular boundaries, and technical leads documenting decisions benefit most. The registry suits teams refactoring component libraries, auditing site quality, planning verifiable feature implementations, or preparing monolith extraction analysis.
How do the architecture analysis skills work together?▼
The modular-decomposition skill runs a sequenced pipeline: component sizing and inventory, shared domain duplication detection, hierarchy cleanup, coupling analysis, then grouping into candidate domain units with optional DDD bounded-context analysis. Coupling-analysis can run standalone using the strength-distance-volatility model for integration health checks.
What licenses and costs apply to these skills?▼
All listed skills are free to use. Web-quality-audit, react-best-practices, and react-composition-patterns carry MIT licenses, while tlc-spec-driven, create-adr, and frontend-blueprint use CC-BY-4.0, requiring attribution to their respective authors.
What prerequisites or boundaries should I know before using these skills?▼
Skills are stack-agnostic but scoped: modular-decomposition requires its prior analysis steps before roadmap planning, react-best-practices excludes composition patterns, and frontend-blueprint covers only visual interfaces, not backend logic or database schemas. The tlc-spec-driven skill ships deterministic validation scripts enforcing structural gates.