domains
Skill0 starsChanged 52 days agoMITView on GitHub
ArcheFlow domain adapters (code, writing, research): terminology, metrics, review focus and context for non-code runs.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- hostinger/hostinger-agent-skillstheir own version, first seen Nov 1, 2026
- vercel/vercel-plugintheir own version, first seen Oct 8, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- vercel/vercel-plugin★ 328same name
- hostinger/hostinger-agent-skills★ 28same 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 repository29 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .cursor/rules/archeflow.mdcCursor rule
- archeflow-reviewSkill
- archeflow-runSkill
- archeflow-sprintSkill
- act-phaseSkill
- autonomous-modeSkill
- check-phaseSkill
- cost-trackingSkill
- custom-archetypesSkill
- dagSkill
- git-integrationSkill
- initSkill
- memorySkill
- multi-projectSkill
- presenceSkill
- progressSkill
- replaySkill
- reportSkill
- reviewSkill
- runSkill
- scanSkill
- scoreSkill
- shadow-detectionSkill
- sprintSkill
- statusSkill
- templatesSkill
- using-archeflowSkill
- workflow-designSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 88
Create .archeflow/domains/<name>.yaml with name, concepts, metrics (minimum required)
- Distinctive: line 95
Reports: use domain-translated terms (e.g., "word count delta" instead of "files changed")
≈ “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
Domain Adapter System
Adapts the PDCA pipeline and archetype system to specific domains (writing, code, research) so events, metrics, reviews, and context use domain-appropriate terminology.
Domain Registry
Domain definitions live in .archeflow/domains/<name>.yaml. Each maps generic concepts to domain-specific equivalents.
Concept Mapping
| Generic Concept | Code | Writing | Research |
| implementation | code changes | draft/prose | draft/analysis |
| tests | automated tests | consistency checks | citation verification |
| files_changed | files changed | word count delta | section count |
| test_coverage | test coverage % | voice drift score | source coverage |
| code_review | code review | prose review | peer review |
| build | build/compile | compile/export | compile (LaTeX/PDF) |
| deploy | deploy | publish | submit/publish |
| bug | bug | continuity error | unsupported claim |
| feature | feature | scene/chapter | section |
Metrics by Domain
| Code | Writing | Research |
| files_changed | word_count | word_count |
| lines_added/removed | voice_drift_score | citation_count |
| tests_added | dialect_density | source_diversity |
| tests_passing | scene_count | claim_count |
| coverage_delta | dialogue_ratio | unsupported_claims |
Review Focus by Domain
| Reviewer | Code | Writing | Research |
| Guardian | security, breaking changes, deps, error handling | plot coherence, character consistency, timeline, continuity | factual accuracy, citation validity, logic, methodology |
| Sage | code quality, coverage, docs, patterns | voice consistency, prose quality, dialect authenticity | argument structure, clarity, tone, completeness |
| Skeptic | design assumptions, scalability, edge cases | premise strength, motivation, ending satisfaction | (default) |
| Trickster | malformed input, races, error paths, dep failures | reader confusion, pacing dead spots, disbelief breaks | (default) |
Model Overrides
Domains can override default model assignments:
| Domain | Override | Rationale |
| Writing | maker: sonnet | Prose quality is the product |
| Writing | custom reviewer: sonnet | Voice evaluation needs taste |
| Research | maker: sonnet | Analysis quality matters |
| Code | (none) | Defaults are calibrated for code |
Context Injection by Domain
Domains declare which extra files agents should read per phase. Context injection is additive (on top of standard ArcheFlow context).
A domain file in .archeflow/domains/ can come with the repository, so its context entries follow the lens rule: only plain relative paths inside the project (letters, digits, ., _, -, /; no leading / or -, no .., no ~, $, backticks, globs or spaces). Skip any other entry with a warning, and read files with the file-reading tool, never through a shell command.
| Phase | Code | Writing |
| always | README.md, config.yaml | voice profile, persona, characters |
| plan | relevant source files, existing tests | series config, previous stories, brief |
| do | Creator's proposal, test fixtures | scene outline, voice profile |
| check | git diff, risk section | voice profile (Sage), outline (Guardian), characters |
Domain Detection
Auto-detects at run.start. Result stored in event stream.
| Priority | Signal | Domain |
| 1 | CLI --domain <name> | as specified |
| 2 | Team preset domain: field | as specified |
| 3 | Writing-domain config exists | writing |
| 4 | *.bib or references/ exists | research |
| 5 | package.json, Cargo.toml, pyproject.toml, go.mod, Makefile | code |
| 6 | No markers | code (default) |
Adding a New Domain
- Create
.archeflow/domains/<name>.yamlwithname,concepts,metrics(minimum required) - Optionally add
review_focus,context,model_overrides - Missing sections fall back to
codedomain defaults - Test with
--domain <name> --dry-run
How Domains Affect Orchestration
- Reports use domain-translated terms (e.g., "word count delta" instead of "files changed")
- Events include domain-relevant metrics in
agent.completeandrun.completepayloads - Reviewers receive domain-specific focus checklists (archetype personality stays the same)
- Context injection adds domain-declared files to each agent's prompt
- Model overrides change which model an archetype uses (interacts with cost-tracking)
- One domain per run. Multi-domain projects use separate runs.
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.