skills.rest
OzeroHAX
OzeroHAXCOMMUNITY
Explore all skills by this author →
GitHub

project-standart-arch

Capture architecture decisions, constraints, and contracts for software projects.

32|7|Updated Jan 28, 2026
Search Tags:#design#planning#architecture#use cases#PRD#risk assessment
One-click install
npx skills add https://github.com/OzeroHAX/AssistAgents --skill project-standart-arch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-standart-arch
Source: https://github.com/OzeroHAX/AssistAgents/tree/main/templates/skills/project/standart/arch
Command: npx skills add https://github.com/OzeroHAX/AssistAgents --skill project-standart-arch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill captures critical architecture decisions, constraints, and contracts early in the development lifecycle, preventing integration and scaling issues before task decomposition begins.

Core Features & Use Cases

  • Architecture Design: Defines components, responsibilities, and data flows.
  • Contract Definition: Documents APIs, events, and schemas.
  • Risk Mitigation: Identifies and plans for risks and constraints.
  • Use Case: Before starting development on a new feature, use this skill to document the system's architecture, ensuring all stakeholders agree on the design and potential risks.

Quick Start

Use the project-standart-arch skill to capture architecture decisions for the new user authentication module.

Frequently Asked Questions about project-standart-arch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document architecture decisions for complex system integrations?▼

Documenting architecture decisions for complex integrations requires capturing components, data flows, and interface contracts early. This prevents scaling issues by defining responsibilities and documenting risks before task decomposition begins.

When do I need to define architecture contracts and constraints for a PRD?▼

You need to define architecture contracts and constraints for a PRD before starting development on new features. This ensures complex integrations, migrations, and public-facing schemas are documented to prevent implementation issues.

What is the best way to design system architecture from use cases?▼

Designing system architecture from use cases involves translating requirements into defined components, data flows, and API schemas. It captures critical constraints and implementation guardrails to mitigate risks early in the lifecycle.

Can I use this architecture design approach for system migrations and public-facing APIs?▼

Yes, this architecture design approach is essential for system migrations and public-facing APIs. It documents events, schemas, and interface contracts while planning for risks to prevent integration failures.

How do I identify and plan for risk assessment during software architecture planning?▼

Risk assessment during software architecture planning identifies potential constraints and implementation bottlenecks early. Documenting these risks and guardrails ensures stakeholders acknowledge potential issues before feature development starts.

Related Skills

Explore More Software Engineering Skills→
proyecto26proyecto26
42

requirements-scoping

Structure ambiguous system design prompts into functional requirements, non-functional constraints, and out-of-scope boundaries.

Official
Intermediate
rsmdtrsmdt
381

specification-compliance

Validate implementations against documented specifications with structured compliance reporting.

Community
Advanced
AgentientAgentient
2

pydantic-v2-strict

Enforce strict-mode data modeling with Pydantic V2 ConfigDict and Field constraints.

Official
Advanced
coolguy1771coolguy1771

architecture-diagrams

Generate system architecture diagrams using Mermaid and PlantUML code.

Community
Intermediate