ship-settings
Skill1 starsChanged 7 months agoMITView on GitHub
View and configure Bayes Ship framework preferences. Settings persist in .claude/state/settings.json.
In this repository43 other files it gives its agents.
- accessibilitySkill
- agent-evalSkill
- agentic-engineeringSkill
- ai-regression-testingSkill
- api-designSkill
- atomic-planningSkill
- backend-patternsSkill
- coding-standards-eccSkill
- context-engineeringSkill
- frontend-patternsSkill
- git-worktreesSkill
- langchain-dependenciesSkill
- langchain-fundamentalsSkill
- langchain-middlewareSkill
- langchain-ragSkill
- langgraph-fundamentalsSkill
- langgraph-persistenceSkill
- minimalist-skillSkill
- output-skillSkill
- redesign-skillSkill
- security-scanSkill
- ship-architectSkill
- ship-autoSkill
- ship-bugfixSkill
- ship-deploySkill
- ship-discoverSkill
- ship-executeSkill
- ship-finish-branchSkill
- ship-newSkill
- ship-planSkill
- ship-researchSkill
- ship-resumeSkill
- ship-reviewSkill
- ship-specSkill
- ship-statusSkill
- ship-testSkill
- ship-worktreeSkill
- soft-skillSkill
- systematic-debuggingSkill
- taste-skillSkill
- test-driven-developmentSkill
- two-stage-reviewSkill
- verification-before-completionSkill
The file
Files
Settings — Configure framework preferences
Available settings
| Setting | Default | Options | Description |
build_mode | guided | guided, autonomous, semi-autonomous | How the build phase runs |
discover_mode | interview | interview, assumptions | Q&A style during discovery |
tdd_mode | strict | strict, relaxed | Strict deletes pre-test code |
auto_commit | true | true, false | Commit after each task |
auto_deploy | false | true, false | Deploy in autonomous mode if creds available |
auto_chain | false | true, false | Auto-advance to next phase after approval |
parallel_waves | true | true, false | Run independent tasks in parallel |
use_worktrees | true | true, false | Use git worktrees for isolation |
model_routing | auto | auto, manual | Use plan model tags or current model |
default_stack | next | next, nest, fastapi, custom | Preferred tech stack |
payment_provider | daraja | daraja, paystack, stripe | Default payment integration |
auth_provider | betterauth | betterauth, nextauth, custom | Default auth library |
visual_companion | true | true, false | Browser mockups during discovery |
Usage
/bayes-ship:ship-settings— show current settings/bayes-ship:ship-settings tdd_mode relaxed— change a setting/bayes-ship:ship-settings reset— reset to defaults
Settings are saved to .claude/state/settings.json.
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.

