standard-application-engineering
暂无简介
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 0
- Forks
- 0
03 SKILL.md 正文
standard-application-engineering
<!-- generated by standards.py from projectious-work/standards; do not edit -->
Binding company standard. The rules below are the summary; the linked file is authoritative. Read only the section the task needs.
Application profiles for engineering standards
Select standards by product behavior, not implementation language. Declare every applicable profile, combine their requirements, and make exceptions explicit and reviewable. Services, workers, and remote MCP servers follow Twelve-Factor App with the listed deviations: layered CLI configuration, local release, development containers, and evidence as a separate channel.
Full standard: .standards/application-profiles.md. Sections:
- Purpose
- Profiles
- Twelve-Factor alignment
- Conditional overlays
- Composite products
- Applicability record
Command-line interface design standard
Each CLI picks one recorded style (ADR): A Unix utility tool [opts] [operands], B verb–resource tool <verb> <type> [<name>] (kubectl), or C
object–action tool <object> <action> (OpenStackClient). All follow the
Unix Philosophy and the baseline: --help with examples, --version,
long names for all options, -- and -, machine envelope as contract, no
secrets in options, prompts only on a TTY, --dry-run for destructive use.
Full standard: .standards/command-line-interface-design.md. Sections:
- Purpose and scope
- Choosing a style
- Baseline for every style
- A. Unix utility style
- B. Verb–resource style (kubectl)
- C. Object–action style (OpenStackClient)
Application configuration standard
Configuration precedence answers which source wins; authority answers whether that source may set the key at all. Preserve both, expose redacted provenance, and never use committed project configuration as an implicit privilege escalation path. Services and workers are environment-first (Twelve-Factor App III); layered files are for CLIs.
Full standard: .standards/application-configuration.md. Sections:
- Purpose and scope
- Precedence
- Authority is separate from precedence
- File and value behavior
- Effective configuration and provenance
- Testing
Application output, logging, and evidence standard
Output answers the request. Logs are a disposable event stream that explains operation (Twelve-Factor App XI). Evidence is a durable record written on purpose that must survive log loss; a log line is never proof. Do not collapse these channels. Structure and redact events before rendering or export.
Full standard: .standards/application-output-logging-and-evidence.md. Sections:
- Purpose and scope
- Three information channels
- Semantic events and rendering
- Streams and formats
- Redaction and data handling
- Failure and correlation
- Evidence integrity
- Testing
Compatibility and machine-interface standard
Treat public and persisted machine interfaces as products. Version their meaning, keep human rendering separate, prove rejection behavior, and never call a change compatible based only on syntactic schema compatibility.
Full standard: .standards/compatibility-and-machine-interfaces.md. Sections:
- Purpose and scope
- Versioning
- Machine-readable results
- CLI profile
- Change classification
- Contract verification
04 同仓库更多 Skills
standard-ui-design
暂无简介
standard-agent-use
Company standard for working with AI agents. Use when deciding what to delegate to agents, capturing open work, keeping agent memory or knowledge notes, improving an agent workflow, or introducing agent work in a team or for a client.
standard-agent-building
暂无简介
skill-management
Manage Skill package manifests as v1 ontology entities.
schema-management
Manage generated processkit schema contracts through deterministic MCP rebuild and inspection workflows.
proposition-management
Record claims, risks, beliefs, world facts, WSJF estimates, and assumptions through the Proposition interface.