architecture-guidelines
Explain architecture strategy and rules to respect all over any realization.
Best use case
architecture-guidelines is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Explain architecture strategy and rules to respect all over any realization.
Teams using architecture-guidelines should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/architecture-guidelines/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How architecture-guidelines Compares
| Feature / Agent | architecture-guidelines | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Explain architecture strategy and rules to respect all over any realization.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
Lexique : - ***project folder*** : Current folder of user, referece too the root of the project folder. - ***documentation files*** : all files containing text explanations, like : spécifications, README, LICENSE, Backlog and all non file writing for human readibility. It could concern media file too, like : image, video, sound, etc... When create or read file or do any kind of software and IT engineering task, always respect thoses rules : - All application must be built over an docker compose v2 architecture. Always use docker compose v2 command to start, stop and manage application. - All services of the application must run into Docker container and must be included into the docker compose file. - All web frontend applications must be implemented with TypeScript and ReactJS - All api services must be implemented with TypeScript - All mobile applications must be implemented with Flutter - All sql database services must use PostgreSql - All tasks of scraping, synchronizing, importing or any other importing and transforming data must be run on backend services. It es forbiden to implemented this kind of task into an API Service. - Only api services can communicate with database servicea web and mobile application must never communicate with database directly. - All frontend or mobile application and backend services must consume api services to access and manipulate data store in database. - All docker compose service must be stored into sperated subfolders of folder /service of the project folder - Architecture specifications must be documented and up to date into the folder /docs/architecture of project folder. Keep project architecture clear and compliant to thoses rules conversational.
Related Skills
cc-skill-project-guidelines-example
Project Guidelines Skill (Example)
c4-architecture
Generate architecture documentation using C4 model Mermaid diagrams. Use when asked to create architecture diagrams, document system architecture, visualize software structure, create C4 diagrams, or generate context/container/component/deployment diagrams. Triggers include "architecture diagram", "C4 diagram", "system context", "container diagram", "component diagram", "deployment diagram", "document architecture", "visualize architecture".
c4-architecture-c4-architecture
Generate comprehensive C4 architecture documentation for an existing repository/codebase using a bottom-up analysis approach.
c-programming-guidelines
Apply for c-programming-guidelines. --- description: globs: **/*.c,**/*.cpp,**/*.h,**/*.hpp,**/*.cxx,CMakeLists.txt,*.cmake,conanfile.txt,Makefile,**/*.cc
backend-guidelines
Comprehensive backend development guide for Node.js/Express/TypeScript microservices. Use when creating routes, controllers, services, repositories, middleware, or working with Express APIs, Prisma database access, Sentry error tracking, Zod validation, unifiedConfig, dependency injection, or async patterns. Covers layered architecture (routes → controllers → services → repositories), BaseController pattern, error handling, performance monitoring, testing strategies, and migration from legacy patterns.
backend-dev-guidelines
Opinionated backend development standards for Node.js + Express + TypeScript microservices. Covers layered architecture, BaseController pattern, dependency injection, Prisma repositories, Zod validation, unifiedConfig, Sentry error tracking, async safety, and testing discipline.
backend-architecture
Design and implement scalable backend infrastructure, microservices, and system architecture patterns.
astro-architecture
Technical architecture for Astro lead generation websites. Use when setting up new projects, configuring build tools, or establishing project foundations. For images use astro-images skill. For SEO use astro-seo skill.
assessing-architecture-quality
Use when assessing codebase architecture and you feel pressure to soften critique, lead with strengths, or frame problems diplomatically - provides evidence-based critical assessment resisting relationship and economic pressures
architecture
Comprehensive system architecture design and implementation workflow that orchestrates expert analysis, technical decision-making, and architectural pattern selection using the integrated toolset. Handles everything from initial system analysis to implementation-ready technical specifications.
architecture-workshop
Framework for designing new architectural mechanisms when existing patterns don't fit
architecture-validator
Validate hexagonal architecture (Domain, Application, Infrastructure, Presentation). Use when creating new files in src/, reorganizing code, or when the user requests architecture validation.