Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

Loslegen

describe-laws-and-style

Sterne6

Forks1

Aktualisiert31. Januar 2026 um 00:59

Distinction between laws (invariants) and style (conventions). Load when determining if a constraint is a law or style.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

adamrdrew

adamrdrew/ushabti

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	describe-laws-and-style
description	Distinction between laws (invariants) and style (conventions). Load when determining if a constraint is a law or style.
user-invocable	false

Laws vs Style

Laws (.ushabti/laws.md):

Non-negotiable invariants that must hold across all Phases, implementations, and refactors
Examples: architectural boundaries, security constraints, correctness guarantees
Laws are absolute — any violation fails a Phase
Only Lawgiver defines or modifies laws

Style (.ushabti/style.md):

Conventions that govern how the system is built
Examples: directory layout, naming conventions, testing strategy, error handling
Style may evolve over time; laws should not
Only Artisan defines or modifies style
Style must never contradict laws

Mehr aus diesem Repository

gleiches Repository

boot-builder

adamrdrew/ushabti

Bootstrap phase context for Builder. Provides current phase, next step, and full phase file contents.

2026-02-116

boot-overseer

adamrdrew/ushabti

Bootstrap phase context for Overseer. Provides phase under review with full file contents and card metadata.

2026-02-116

approve-phase

adamrdrew/ushabti

Approve a phase — sets status to complete, marks all steps reviewed, updates linked card. Use when declaring a phase green.

2026-02-116

create-phase-files

adamrdrew/ushabti

Create a phase directory with all required files in one call. Use instead of separate mkdir + Write calls when creating a new phase.

2026-02-116

kick-back-phase

adamrdrew/ushabti

Kick a phase back to building — sets status and adds new step entries to progress.yaml. Use when requesting fixes from Builder.

2026-02-116

mark-step-done

adamrdrew/ushabti

Mark a step as implemented in progress.yaml with notes and touched files. Use after completing each step instead of manual Edit calls.

2026-02-116

name	describe-laws-and-style
description	Distinction between laws (invariants) and style (conventions). Load when determining if a constraint is a law or style.
user-invocable	false

Laws vs Style

Laws (.ushabti/laws.md):

Non-negotiable invariants that must hold across all Phases, implementations, and refactors
Examples: architectural boundaries, security constraints, correctness guarantees
Laws are absolute — any violation fails a Phase
Only Lawgiver defines or modifies laws

Style (.ushabti/style.md):

Conventions that govern how the system is built
Examples: directory layout, naming conventions, testing strategy, error handling
Style may evolve over time; laws should not
Only Artisan defines or modifies style
Style must never contradict laws