saint-graves/sica-fondt
1
0
Fork 0
mirror of https://github.com/SHOGGOTH-SECTOR/sica-fondt.git synced 2026-07-31 16:16:26 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update ONBOARDING.md

Browse Source
This commit is contained in:
gravermistakes 2026-06-22 14:18:58 -07:00 committed by GitHub
parent 4a1575f1a3
commit dd2c038ef9
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 6 additions and 51 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

57
ONBOARDING.md
View File

@ -1,24 +1,3 @@
# Welcome to sica-fondt
## How We Use Claude
Based on Claude's usage over the last 30 days:
Work Type Breakdown:
_TODO — no per-session detail was available to classify. We can fill this in
once there are a few sessions of history to scan._
Top Skills & Commands:
/update-config ████████████████████ 3x/month
/compact ███████░░░░░░░░░░░░░░ 1x/month
/deep-research ███████░░░░░░░░░░░░░░ 1x/month
/session-start-hook ███████░░░░░░░░░░░░░░ 1x/month
/fewer-permission-prompts ███████░░░░░░░░░░░░░░ 1x/month
/design-sync ███████░░░░░░░░░░░░░░ 1x/month
/run-skill-generator ███████░░░░░░░░░░░░░░ 1x/month
Top MCP Servers:
GitHub ████████████████████ 5 calls
## Your Setup Checklist
@ -31,7 +10,6 @@ Top MCP Servers:
### Skills to Know About
- /update-config — configure the Claude Code harness via settings.json (permissions, env vars, hooks). The team's most-used command; reach for it for any "from now on when X…" automation.
- /session-start-hook — set up a SessionStart hook so the repo's toolchains/tests are ready in every web session. This repo uses one to install ponyc/Alire/GnuCOBOL.
- /run-skill-generator — author the per-project `run-<unit>` skill that tells agents how to build, launch, and drive the app. Already produced `run-sica-fondt`.
- /deep-research — fan-out, fact-checked, cited research reports when you need to investigate a topic in depth.
- /fewer-permission-prompts — scan transcripts and add a read-only allowlist to `.claude/settings.json` to cut down on permission prompts.
- /compact — free up context by summarizing the conversation so far on a long session.
@ -61,38 +39,15 @@ Top MCP Servers:
## Get Started
Your first task: get the project running end-to-end and read the map. Not sure
which doc to read for what? Start with [`AGENTS.md`](AGENTS.md) — it's the
signpost to every other document here.
Your first task: get the project running end-to-end and read the map. Not sure which doc to read for what? Start with [`AGENTS.md`](AGENTS.md) — it's the directions for every other document here.
1. Open the repo and let the SessionStart hook finish installing toolchains.
2. Run the smoke driver to confirm everything builds and runs:
`.claude/skills/run-sica-fondt/smoke.sh` — you want `smoke: ALL GREEN`.
3. Read `README.md`, `SOUL.md`, and `docs/` (start with
`docs/bus-topology.md` and `docs/gen03_state_of_architecture.md`) to
understand the organ/border model (Ichor bus → Ada D1 border → inner brain;
the COBOL invariant vault).
2. Run the smoke driver to confirm everything builds and runs: `.claude/skills/run-sica-fondt/smoke.sh` — you want `smoke: ALL GREEN`.
3. Read `README.md`, and `docs/` (start with `docs/bus-topology.md` and `docs/gen03_state_of_architecture.md`) to understand the organ/border model (Ichor bus → Ada D1 border → inner brain; the COBOL invariant vault).
4. Pick up a small design-sync or build task from there. Ask Claude to walk you
through any unit — it has the `run-sica-fondt` skill loaded.
<!-- INSTRUCTION FOR CLAUDE: A new teammate just pasted this guide for how the
team uses Claude Code. You're their onboarding buddy — warm, conversational,
not lecture-y.
<!-- INSTRUCTION FOR CLAUDE:
Open with a warm welcome — include the team name from the title. Then: "Your
teammate uses Claude Code for [list all the work types]. Let's get you started."
Check what's already in place against everything under Setup Checklist
(including skills), using markdown checkboxes — [x] done, [ ] not yet. Lead
with what they already have. One sentence per item, all in one message.
Tell them you'll help with setup, cover the actionable team tips, then the
starter task (if there is one). Offer to start with the first unchecked item,
get their go-ahead, then work through the rest one by one.
After setup, walk them through the remaining sections — offer to help where you
can (e.g. link to channels), and just surface the purely informational bits.
Don't invent sections or summaries that aren't in the guide. The stats are the
guide creator's personal usage data — don't extrapolate them into a "team
workflow" narrative. -->
Open with a warm welcome — then check what's already in place against everything under Setup Checklist (including skills), using markdown checkboxes — [x] done, [ ] not yet. Lead with what they already have. One sentence per item, all in one message.
The guides are universal, please extrapolate them into a "team workflow" narrative. -->