Loading...
Loading...
Found 288 Skills
Helps engineering managers break down knowledge silos and build sustainable documentation and collaboration practices — produces a four-root-cause diagnostic for silos, an Engineering Guilds framework, a minimum-viable documentation approach using ADRs, a structured onboarding model, and a cross-team request decision framework. Use when the user says "knowledge silos," "reinventing the wheel," "nobody reads docs," "onboarding is bad," "teams don't talk," "documentation culture," "cross-team friction," "information doesn't flow," or "new hires struggle to ramp up."
Validates completeness and consistency of the project architecture against all GDDs. Builds a traceability matrix mapping every GDD technical requirement to ADRs, identifies coverage gaps, detects cross-ADR conflicts, verifies engine compatibility consistency across all decisions, and produces a PASS/CONCERNS/FAIL verdict. The architecture equivalent of /design-review.
Guided, section-by-section authoring of the master architecture document for the game. Reads all GDDs, the systems index, existing ADRs, and the engine reference library to produce a complete architecture blueprint before any code is written. Engine-version-aware: flags knowledge gaps and validates decisions against the pinned engine version.
Write a structured architecture decision document — an RFC / design doc / technical doc that records *why* a non-trivial technical choice was made, not just what was built. Follows a six-part method: contextualize for a newcomer, state the architecturally-relevant requirements, design components against them with static + dynamic diagrams, weigh every alternative by pros / cons / risks (each risk with impact, probability, mitigation, contingency), record the decision and how it was made, then conclude and communicate. Writes in the language of the request. Reach for it whenever someone is choosing between technical options or documenting one — "write an RFC", "design doc", "architecture decision", "ADR", "tradeoff analysis", "technical documentation of an implementation", "help me decide between X and Y" — even if they never say "RFC". Also fits the retrospective variant: documenting an implementation after the fact (lessons learned, version history).
Track and manage construction warranties. Monitor expiration dates, claims, and manufacturer documentation.
Best practices for TypeScript types, interfaces, assertions, and type safety. Use when writing or reviewing TypeScript code.
Automate construction permit tracking and management. Monitor application status, track renewal deadlines, manage document requirements, and integrate with municipal systems.
Implement animations using the Motion library. Use when adding motion, transitions, gestures, scroll effects, or interactive animations to components. Triggered by implementation requests, not conceptual discussions.
Build Spring Boot 4.x applications following best practices. Use when developing or modifying Spring Boot apps that use Spring MVC, Spring Data JPA, Spring Modulith, Spring Security, or Spring Boot testing including package structure, REST APIs, entities/repositories, service layer, modular monoliths, and REST API tests.
Convert CAD/BIM files to structured data. Extract element data from Revit, IFC, DWG, DGN files.
Extract quantities from BIM/CAD data for cost estimation. Group by type, level, zone. Generate QTO reports.
Automated cost estimation from BIM models using DDC CWICR database with 55,719 work items. AI classification + vector search for accurate pricing.