Results for “architect”

Brainstorm five unique, memorable product names with rationale aligned to brand values and target audience.

Generate structured, machine-readable implementation plans for features, refactoring, upgrades, or infrastructure changes.

Tests approaches at extreme scales to reveal fundamental limits and strengths hidden at normal scales.

Design and implement AWS architectures with best practices for IAM, S3, Lambda, DynamoDB, and serverless deployments.

Builds single-page applications with component-based architecture, dependency injection, reactive forms, and routing.

GraphQL query language and runtime for APIs enabling clients to request exactly the data they need with strongly-typed schemas and single endpoint architecture.

Write or maintain technical documentation — READMEs, runbooks, API references, architecture docs — that a specific reader can act on without asking follow-ups.

Use when the user asks to design RAG pipelines, optimize retrieval strategies, choose embedding models, implement vector search, or build knowledge retrieval systems.

Design the architecture for a multi-command skill system — the shared state schema, the command map, the router, and the boundary each command stops at — before any skill files get written. Use when the user wants to turn one skill into a system, combine several related or overlapping skills into a single coherent one, build a skill with subcommands (like `/thing audit`, `/thing polish`), design a suite, family, or collection of skills, or asks "how should I structure this skill set". Also trigger on "skill system", "skill architecture", "multi-command skill", "system of skills", "make these skills work together", "skill with slash commands", or complaints that their skills overlap, collide, duplicate each other, or never fire. Produces an architecture spec only — it never writes SKILL.md or reference files. Hand the finished spec to skill-creator to build from.

Audit, write, or revise Architecture Decision Records (ADRs), including the decision of whether one is warranted. Use when an architecturally significant decision needs recording, when reviewing an existing ADR collection, or when adding ADRs to a project that has none. Detects existing template (Nygard or MADR) and defaults to Nygard for new repos. Gates comparison ADRs through a decompose-and-verify interview before drafting.

Generates a comprehensive developer onboarding guide from a codebase, covering tech stack, setup, architecture, conventions, and troubleshooting.

Applies ITIL principles to design scalable, maintainable, and interoperable enterprise systems and solutions.

Researches and recommends programming technologies, libraries, and architectural approaches with verified references from official documentation.

Use when building NestJS applications requiring modular architecture, dependency injection, or TypeScript backend development. Invoke for modules, controllers, services, DTOs, guards, interceptors, TypeORM/Prisma.

Review an entire codebase for architecture, engineering health, and exploitable risk; generate a prioritized remediation plan, an evidence-anchored system knowledge document, or both.

Conduct technical research on technologies and architecture. Use when the user says they would like to do or produce a technical research report

Use this when reviewing a full system design, architecture plan, or cross-service implementation for operational risk, boundary clarity, security posture, deployability, and maintainability.

Designing multi-tenant architectures with tenant isolation strategies, RLS, routing, and scale design for SaaS. Use when designing multi-tenant SaaS systems or tenant isolation.

Write, review, and maintain architecture decision records with clear context, alternatives, consequences, and lifecycle governance. Use when a consequential technical decision must remain understandable.

Read every ADR markdown file in docs/adr before making or reviewing decision-sensitive changes. Use when architecture, conventions, or tradeoffs are involved.

SERP-based semantic topic clustering for content architecture planning. Groups keywords by actual Google SERP overlap (not text similarity), designs hub-and-spoke content clusters with internal link matrices, and generates interactive visualizations. Optionally executes content creation if claude-blog is installed. Use when user says "topic cluster", "content cluster", "semantic clustering", "pillar page", "hub and spoke", "content architecture", "keyword grouping", or "cluster plan".

Designs, reviews, and scales backend systems with detailed blueprints, trade-off analysis, and technology recommendations.

Generates immersive, high-performance web interfaces with advanced motion design, typography, and architectural craftsmanship.

Review C#/.NET code for design pattern implementation and suggest improvements without making changes.

Select and design navigation patterns that match product structure, user tasks, and platform conventions.

Quizzes users on Information Retrieval concepts, including Elasticsearch architecture and probabilistic models like BM25, with concise feedback.

Tests approaches at extreme scales (1000x bigger/smaller, instant/year-long) to expose fundamental truths hidden at normal scales.

Convierte especificaciones aprobadas en un plan técnico detallado, documentando decisiones de arquitectura, flujo de datos y cambios de archivos.

Designs and implements CDN architectures, optimizing cache strategies, edge computing, and security for global content delivery.

Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.

Write Architectural Decision Records following MADR template. Applies Definition of Done criteria, marks gaps for later completion. Use when generating ADR documents from extracted decisions.

Review a code file or directory and produce an evidence-backed GitHub or Jira issue proposing bug fixes, performance improvements, modularity improvements, DRY refactors, file splitting, reusable helpers, and architecture-alignment work. Use when a user asks for a code review, technical-debt proposal, refactor proposal, quality audit, bug-risk review, architecture-alignment review, or issue creation. This skill proposes work; it does not modify code.

Create and manage Amazon EventBridge event buses, rules, event patterns, and targets for event-driven architectures.

Generates production-ready Terraform files for AWS infrastructure, writing complete .tf files for any cloud architecture without deploying.

Generates thorough README.md documentation by exploring a codebase, identifying the tech stack, and producing setup, architecture, and deployment guides.

Maintains a PARA-structured knowledge base on disk for persistent project context, decisions, and architecture records across agent sessions.