keez97
- 7 skills
- 0 followers
- 8 hours ago last updated
- ▌ Describe Design · keez97Reverse-engineer existing codebases and produce architectural documentation with Mermaid diagrams (C4, sequence, ER, deployment). Use this skill whenever the user asks to document a codebase, explain how a system works, create architecture diagrams, build onboarding documentation, generate a system overview, map dependencies, or describe the design of an existing project. Also trigger when someone says "how does this work", "describe the design", "document this for the team", "create a C4 diagram", "I inherited this codebase", or asks for architecture documentation of any kind. If the user wants to understand an existing system rather than design a new one, this is the right skill.
- ▌ Cloud Infrastructure · keez97AWS and infrastructure-as-code expert for Python/FastAPI full-stack apps. Use this when you need cloud architecture design, infrastructure review, Terraform/CDK implementation, cost optimization, or deployment strategy. Covers Lambda, ECS, RDS, VPC, IAM, networking, and production AWS patterns. Triggers on: AWS, Terraform, CDK, cloud architecture, infrastructure, Lambda, ECS, RDS, Aurora, deployment, serverless, VPC, IAM, cost, infrastructure-as-code, CloudFormation, scaling, security, databases.
- ▌ Architecture Workflow · keez97 bundleEnd-to-end codebase health workflow: discover architecture, review it, fix issues with TDD, and document the result. Chains describe-design, architecture review skills, and tdd-ai into a single phased workflow with checkpoint documents. Use this skill whenever the user says "audit my codebase", "do a full architecture review and fix things", "improve my codebase architecture", "health check this project", "review and refactor", "clean up this codebase", or any request that involves understanding an existing codebase, identifying architectural problems, fixing them, and documenting the result. Also trigger when the user wants a comprehensive codebase improvement that goes beyond a single review — they want the full loop of discover, diagnose, fix, and re-document. If the user seems to want both a review AND fixes applied, this is the right skill.
- ▌ Software Architecture · keez97Design scalable systems with Clean Architecture, SOLID principles, and Architecture Decision Records. Use this for decomposing systems, choosing architectural patterns, documenting decisions, and avoiding over-engineering. Language-agnostic: applies to any tech stack.
- ▌ Microservices Architect · keez97Design distributed systems using microservices patterns. Triggers on: microservices, service mesh, distributed systems, event-driven architecture, saga pattern, service boundaries, monolith to microservices, API gateway, message queue, eventual consistency, circuit breaker, gRPC, service decomposition. Provides ADRs, service boundary diagrams, API contracts, data flow analysis, and failure mode assessments. Remember: distributed systems are HARD. Every service boundary is a network call.
- ▌ Python Architecture Review · keez97 bundleExpert-level architecture review and design guidance for Python backends, with deep knowledge of FastAPI, PostgreSQL, async patterns, and modern Python project structure. Use this skill whenever the user asks you to review Python code architecture, design a new Python backend, evaluate project structure, assess API design, review database schemas, audit security posture, or discuss scalability of a Python service. Also trigger when the user shares Python backend code and asks "what do you think", "is this structured well", "how should I organize this", or describes a new feature/service they're planning to build in Python. Even if they don't say "architecture" explicitly — if they're asking about how to structure a FastAPI app, design their models, or whether their approach will scale, this skill applies.
- ▌ Modern Web App Architecture · keez97Expert frontend architecture review and design for modern web apps. Review existing apps against rendering strategy, state management, Core Web Vitals, bundle efficiency, and project structure. Design new apps with concrete ADRs, performance budgets, and migration paths. Catch bundle bloat, state leaks, hydration mismatches, and performance gaps before they hit production. Stop shipping unnecessary JavaScript.