Tags

Cross-cutting clusters for rules, patterns, principles, and mechanisms. Tags avoid duplicating page type, review status, and compactness metadata.

Guidance tags

Change ShapeChange boundaries: what belongs together, what should split, and how much work one review should carry.68 items DependenciesThird-party code: selection, version bounds, updates, and downstream exposure.18 items Module LayoutModule and file placement, ownership, crate-root navigation, and public re-export paths.20 items OwnershipWhere behavior and state belong, and which module or layer should make the decision.38 items Public APIInterfaces and behavior that callers may depend on across a crate or system boundary.70 items Reader LocalityDefinitions, decisions, and use sites kept near enough that a change does not require a repository tour.91 items RefactoringInternal structural changes that should leave externally relevant behavior intact.10 items ReleaseVersioning, package contents, support claims, and checks required before publication.12 items ReviewabilityCode, prose, and proof arranged so a reviewer can find the decision and check it.107 items RustRust library and application practice, including idioms that do not transfer directly to other languages.104 items

AsyncTask spawning, scheduling, partial results, and failure behavior across asynchronous boundaries.7 items Boundary CorrectnessParsing, normalization, adapters, and policy where representations or systems meet.64 items ErrorsError types and context carried between callers, layers, and user-facing surfaces.23 items Failure OutputWhat a user, test, or operator sees when work fails.25 items ObservabilityLogs, diagnostics, and durable failure signals at the boundary that owns them.20 items Security PrivacySecrets, capabilities, unsafe code, diagnostic data, and other trust-boundary concerns.21 items Side EffectsWrites, network calls, process launches, and other work outside a pure computation.26 items State TransitionsValid states and the named transitions that move a system between them.22 items Validation PolicyWhich inputs are accepted, rejected, normalized, or allowed to fall back.31 items

PerformanceMeasured cost and latency, plus the benchmark discipline needed to justify an optimization.15 items TestingExecutable checks for contracts, edge cases, regressions, and useful failure messages.52 items VerificationEvidence for a claim: checks, inspection, measurements, or comparison with a trusted source.103 items

AIWriting shaped with AI: generated-prose tells, checked claims, curation, and author ownership.7 items DocumentationREADME, guide, reference, and contract prose used to understand current behavior.111 items ExamplesSmall uses that teach an API or prove an integration path.16 items Local ConventionsEstablished repository rules and language idioms, followed consistently unless the work changes them.31 items RustdocRust API documentation as rendered and navigated by a crate user.20 items Source TruthThe implementation, primary source, or maintained artifact that settles a disputed claim.81 items

Agent ContextInstructions and durable project facts loaded for an agent's current task.45 items Agent WorkflowHow coding-agent work is scoped, executed, checked, and handed back.74 items AutomationChecks and maintenance run mechanically instead of being remembered each time.39 items Feedback LoopsFast checks, review cycles, and ways to turn repeated feedback into durable guidance.16 items Generated ArtifactsFiles or behavior produced from another source: ownership, regeneration, validation, and promotion.5 items Review HandoffThe context and evidence another person needs to continue or judge the work.51 items ToolingCommands and interfaces that make a preferred workflow repeatable.60 items VCS JJJujutsu working-copy, change, workspace, bookmark, remote, and recovery practice.39 items