Keeping the docs layer from drifting away from the code.
- [tester](https://github.com/NirDiamant/Agentic_Engineering/tree/main/skills/tester): Test authoring support.
- [testify](https://github.com/NirDiamant/Agentic_Engineering/tree/main/skills/testify): Test generation and verification.
## Evaluation
- [eval](https://github.com/NirDiamant/Agentic_Engineering/tree/main/eval):
Complete documentation covers architecture, data models, business processes, authorization, and component relationship diagrams.
- [API Testing Tools](https://happyin.space/architecture/api-testing-tools/): Practical tools for testing, debugging, and validating APIs during development
control what survives compaction:
## Compact Instructions
When summarizing, always preserve: file paths, errors, test results, decisions, TODOs.
tags for critical rules:
NEVER run DROP without WHERE clause.
Update CLAUDE.md after
thing that set it disappears.
## The routes that don't work, tested
It is worth recording the dead ends, because they look plausible and cost a day each.
**Private
creating CLI applications to automations. Agents are automatically scored based on deterministic and semantic tests using a specialized auditing agent.
Additional features include agent continuation (automatically providing follow-up prompts
only/REPOSITORY_MAP.md): source tree and where each feature lives.
- [Build and test](for-ais-only/BUILD_AND_TEST.md): make targets, unit and integration loops, mkdocs build.
- [Failure modes](for-ais-only/FAILURE_MODES.md
pinned).
- **Write safety:** Seekstone ships a named Write-Safety Contract (docs/WRITE-SAFETY.md) of ten tested guarantees: zero network/telemetry, vault sandbox, byte-identical frontmatter on body edits, atomic writes (no torn files
bead init --prefix
## Create first bead
bead create \
--title 'Add a CONTRIBUTING.md so that test -s CONTRIBUTING.md passes. Work on this issue directly.' \
--description 'Create CONTRIBUTING.md with contribution guidelines. Acceptance
registry of where the project's
documentation lives, the exact lint / type-check / test / build commands for the
repo, its coding guidelines, its branch-and-landing (`git-workflow`) flow
covering one supported workflow — a 60-minute review, one configured local gate, its regression test, and written rollout/rollback proof within two business days. Current terms: https://thumbgate.ai/pricing
- Enterprise: custom
Check the `Content-Type` response header in the Network tab.
- Add a non-ASCII test string (`café — 日本語 — 🌍`) to a page and confirm it renders correctly.
### Sources
- HTML Living Standard
connection closes, SQLite close is serialized under the write lock, and the full Brain test workflow has enough time to finish instead of cancelling slow-but-valid runs. Builds
need — it won't touch or interfere with any system Git.
> **Android / Termux:** The tested manual path is documented in the [Termux guide](https://loki.computer/docs/getting-started/termux). On Termux, Loki installs