Define modular boundaries and naming conventions for Sage applications.
npx skills add https://github.com/majiayu000/sage --skill sage-architecture
Please help me install this Agent Skill. Skill: sage-architecture Source: https://github.com/majiayu000/sage/tree/main/.sage/skills/sage-architecture Command: npx skills add https://github.com/majiayu000/sage --skill sage-architecture
This Sage architecture guide provides a cohesive blueprint to structure large Sage projects, reducing fragmentation and enabling scalable collaboration across teams.
Start by auditing modules for boundaries, then codify layer responsibilities and naming conventions in the repo docs. Use this guide during planning and reviews to keep Sage architecture coherent.
High-intent search queries and answers about installing and using this skill.
To enforce module boundaries for maintainability, keep every module under 200 lines and split larger ones into submodules. Define explicit interfaces and layered responsibilities to reduce cross-cutting concerns across cli, sdk, core, and tools components.
The best way to plan a refactor for a fragmented structure is applying architectural guidelines to decompose the project into smaller, coherent modules. Document module boundaries and naming conventions to ensure consistent governance during the restructuring process.
Defining layered responsibilities involves assigning clear, specific duties to cli, sdk, core, and tools components to reduce cross-cutting concerns. Document these layer responsibilities and enforce them through regular code reviews and tooling checks.
Project structure chaos happens when large projects lack cohesive blueprints, leading to fragmentation. You need modular design guidelines when scaling collaboration across teams, ensuring consistent naming, boundaries, and RFC-compliant module schemas for onboarding.
Yes, you can use these architecture guidelines for both new planning and existing project governance. They apply to planning, refactoring, and governance tasks by codifying layer responsibilities and maintaining boundaries through code reviews and tooling.
Relying solely on naming conventions limits code organization because it does not enforce structural boundaries. You must also document module schemas, define layered responsibilities, and use tooling to maintain governance across cli, sdk, core, and tools.
DanielMSchmidtAnalyze Weave Steps architecture decisions and invariants before making changes.
gonzaloserranoAudit Go modules and generate compliance checklists against engineering guidelines.
pradyumnasagarGuide authors through creating and validating ORS SKILL.md files.
BarryrnPlan and document software architecture decisions with a structured decision framework.
