Run any Skill in Manus with one click

arch-guidance

Stars19

Forks2

UpdatedFebruary 11, 2026 at 09:31

Consult and apply the repository architecture reference when discussing system architecture, module boundaries, directory layout, service interfaces, Docker Compose, Kubernetes deployment, or operational entry points. Use when a user asks about architecture, refactors, project structure, deployment models, or infra layout.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

c9r-io

c9r-io/orchestrator

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	arch-guidance
description	Consult and apply the repository architecture reference when discussing system architecture, module boundaries, directory layout, service interfaces, Docker Compose, Kubernetes deployment, or operational entry points. Use when a user asks about architecture, refactors, project structure, deployment models, or infra layout.

Architecture Guidance

When triggered:

Read docs/architecture.md first.
Use it as the source of truth for directory conventions (core/, portal/, docker/, k8s/, deploy/, scripts/, docs/qa/, docs/ticket/) and platform workflow.
If the requested change conflicts with the reference, call out the conflict and propose an updated, consistent design.

If the project is a generated app (from project-bootstrap), assume the conventions exist unless the repo shows otherwise.

More from this repository

same repository

security-test-doc-gen

c9r-io/orchestrator

Generate and complete reusable security test documents under docs/security/ based on the current project implementation and/or a confirmed plan. Use when a developer asks to complete security test docs, add missing security scenarios, or establish a security test baseline for the project.

2026-07-2619

uiux-test-doc-gen

c9r-io/orchestrator

Generate and maintain reusable UI/UX test documents under docs/uiux/ based on the current project UI implementation and the design-system constraints. Use when a developer asks to complete UI/UX test docs, add missing UI/UX scenarios, align UI constraints, or wants UI consistency/a11y/responsive regression checks during development.

2026-07-2619

orchestrator-guide

c9r-io/orchestrator

Guide for working with the Agent Orchestrator — a CLI tool for AI-native SDLC automation. Use when writing or editing YAML manifests (Workspace, Agent, Workflow, StepTemplate, ExecutionProfile, SecretStore, EnvStore, Trigger, CRD), running orchestrator CLI commands, designing workflow step pipelines, writing CEL prehook/finalize expressions, configuring triggers (cron/event-driven task creation), or configuring self-bootstrap workflows. Triggers: any mention of orchestrator config, YAML manifests with "orchestrator.dev/v2", workflow steps, prehooks, finalize rules, task create/start/pause, orchestrator run, step filtering, direct assembly, agent capabilities, StepTemplate prompts, execution profiles, sandbox configuration, secret management, or trigger/cron scheduling.

2026-07-2519

fr-governance

c9r-io/orchestrator

Govern feature request (FR) documents through their full lifecycle — from planning to implementation to closure. Use when the user asks to govern/治理 a feature request, close an FR, check FR status, or says "治理FR", "/fr-governance". Scans docs/feature_request/ for open FR docs, plans implementation, executes governance, and self-checks closure.

2026-07-2519

qa-doc-gen

c9r-io/orchestrator

Generate or update QA/security/UIUX test documentation after confirmed feature implementation plans or completed refactors. Use this skill AFTER plan approval or code completion to: (1) add new QA test docs for new behavior, (2) generate design docs, and (3) run repo-wide cross-doc impact analysis (docs/qa/, docs/security/, docs/uiux/, docs/guide/ and its translations, docs/design_doc/, docs/showcases/, root Markdown including CHANGELOG.md, and .claude/skills/) to update stale steps, expectations, and assertions. Triggers when users ask to create QA docs, update test docs after implementation, or sync QA/security/UIUX docs after behavior changes.

2026-07-2519

qa-doc-governance

c9r-io/orchestrator

Govern and periodically remediate QA documentation quality across docs/qa, docs/security, and docs/uiux. Use when users ask to audit QA docs, run recurring documentation checks, fix doc drift after refactors, enforce scenario limits/checklists/UI entry visibility, or synchronize README/manifest/changelog consistency.

2026-07-2519

name	arch-guidance
description	Consult and apply the repository architecture reference when discussing system architecture, module boundaries, directory layout, service interfaces, Docker Compose, Kubernetes deployment, or operational entry points. Use when a user asks about architecture, refactors, project structure, deployment models, or infra layout.

Architecture Guidance

When triggered:

Read docs/architecture.md first.
Use it as the source of truth for directory conventions (core/, portal/, docker/, k8s/, deploy/, scripts/, docs/qa/, docs/ticket/) and platform workflow.
If the requested change conflicts with the reference, call out the conflict and propose an updated, consistent design.

If the project is a generated app (from project-bootstrap), assume the conventions exist unless the repo shows otherwise.