bulwark
Skill2 starsChanged 31 days agoApache-2.0View on GitHub
Maintain frontend module boundaries and reusable design artifacts with demonstrable checks. Use for architecture erosion, stale abstractions, and design-system integration.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- obstalabs/bulwarktheir own version, first seen Oct 29, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- obstalabs/bulwark★ 5same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository37 other files it gives its agents.
- canonSkill
- colorSkill
- formSkill
- graphicsSkill
- layoutSkill
- motionSkill
- pilotSkill
- systemsSkill
- typeSkill
- holdfastSkill
- aegisSkill
- assaySkill
- flightlineSkill
- gaugeSkill
- groundworkSkill
- gungnirSkill
- husbandrySkill
- load-bearingSkill
- pilotSkill
- plumbSkill
- stationkeepingSkill
- crucibleSkill
- envoySkill
- forgeSkill
- ledgerSkill
- prospectSkill
- reckoningSkill
- forageSkill
- touchstoneSkill
- bearingsSkill
- keelSkill
- liverySkill
- lookoutSkill
- pilotSkill
- seaworthySkill
- trialsSkill
- wellspringSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 41
When this stage is fulfilled: checklist advance locate --run "$RUN".
- Distinctive: line 58
Verify consumers and update usage examples or migration notes.
- Distinctive: line 71
Do not extract a framework solely to eliminate visual repetition.
- Very specific: line 73
If an input or permission is missing, name the blocker and leave the relevant item pending.
- Very specific: line 79
After all required work and stage closures is recorded, use checklist done --run "$RUN".
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!--
Copyright 2026 IamK77 — Licensed under the Apache License, Version 2.0.
See ./LICENSE and ./NOTICE · https://www.apache.org/licenses/LICENSE-2.0
-->bulwark
Maintain frontend module boundaries and reusable design artifacts with demonstrable checks. Use for architecture erosion, stale abstractions, and design-system integration.
Inputs
Observed maintenance problem; affected modules/components; current dependency rules and tests; ownership and compatibility constraints.
Run record
Use checklist 0.5 or newer for this SOP. Reading or reloading the skill must not reset work. For a new task, run checklist init "${CLAUDE_SKILL_DIR}" --new --path "/absolute/project"; retain its returned ID as RUN. For existing work, use checklist resume "$RUN", then checklist show --run "$RUN". Outside Claude, replace the skill-directory variable with this directory’s actual path.
Commands below record work after it is done. Replace evidence placeholders with concise artifact locations and observations. Manual confirmations are not independent proof; a sensor pass covers only the command and inputs it observed. verify does not close a stage; advance checks that its required readings are fulfilled. Use report --run "$RUN" for the retained history.
Procedure
locate
Identify a concrete boundary violation, duplication, or maintenance bottleneck. Trace affected consumers and decide which behaviour and APIs must remain stable.
Record these artifacts after doing the work:
- The maintenance problem is supported by concrete code/change evidence.
checklist check locate problem --run "$RUN" --evidence "<artifact and observation>" - Affected consumers and compatibility boundaries are known.
checklist check locate consumers --run "$RUN" --evidence "<artifact and observation>"
When this stage is fulfilled: checklist advance locate --run "$RUN".
repair
Make a coherent boundary or component change. Add a targeted import/contract/regression check and deliberately violate the rule to show the check catches it; restore the code afterward.
Record these artifacts after doing the work:
- The responsible boundary or abstraction is repaired.
checklist check repair change --run "$RUN" --evidence "<artifact and observation>" - A retained check detects a representative violation and the probe is restored.
checklist check repair guard --run "$RUN" --evidence "<artifact and observation>"
When this stage is fulfilled: checklist advance repair --run "$RUN".
handoff
Verify consumers and update usage examples or migration notes. Assign unresolved cross-team changes to an owner rather than hiding them in a local rule.
Record these artifacts after doing the work:
- Affected consumers and relevant checks were exercised.
checklist check handoff consumers --run "$RUN" --evidence "<artifact and observation>" - Usage, migration guidance, and unresolved ownership are documented.
checklist check handoff migration --run "$RUN" --evidence "<artifact and observation>"
When this stage is fulfilled: checklist advance handoff --run "$RUN".
Branches
Do not extract a framework solely to eliminate visual repetition. Systems provides selected tokens/component contracts; this SOP integrates and protects them rather than dictating creative direction.
If an input or permission is missing, name the blocker and leave the relevant item pending. A changed requirement may need a new run; an accepted checklist edit uses resume "$RUN" --refresh and requires fresh readings. To abandon work, use checklist reset --run "$RUN" --reason "<reason>"; history is retained.
Completion
A boundary-preserving maintenance change with a meaningful retained check and consumer migration evidence.
After all required work and stage closures is recorded, use checklist done --run "$RUN". This archives the result without deleting its history; it does not authorise any external action.
Reference shelf
Open the technique relevant to the current step. These notes provide concrete methods and examples, not additional phases; this entrypoint defines the run's completion conditions.
- Align component ownership with actual consumers
- Retain a check for a meaningful module boundary
- Improve a measured contributor feedback loop
- Protect frontend-facing boundaries without trusting the surface alone
- Remove unused or superseded frontend structure safely
- Maintainable boundaries and consumers
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.