mirror of
https://github.com/fabro-sh/fabro.git
synced 2026-09-07 08:27:12 +00:00
283eab181f
Invert the docs convention so the Mintlify-published site lives under docs/public/ and internal artifacts (strategy docs, brainstorms, plans, etc.) sit at docs/ root or docs/internal/. Tools that default to writing into docs/ now land in the catch-all instead of leaking into the published tree. - Move Mintlify content (administration/, agents/, api-reference/, changelog/, core-concepts/, examples/, execution/, getting-started/, human-tools/, integrations/, languages/, reference/, tutorials/, workflows/, images/, logo/, docs.json, favicon.svg, dot-highlight.js) into docs/public/. - Collapse docs-internal/ into docs/internal/. - Update Rust path references (fabro-api/build.rs, fabro-server, fabro-dev), TypeScript generator arg, CI path filters, clippy.toml reasons, AGENTS.md/CLAUDE.md, and README.md image refs. Mintlify dashboard project root must be updated to docs/public/ in a follow-up. .mintignore move/trim and .claude/skills/ updates land in a separate commit.
827 B
827 B
Fabro Personas
Fabro is for expert engineers who want to encode software processes as workflows.
Primary users
- Solo expert engineer: runs workflows locally to automate planning, implementation, testing, and review loops.
- Tech lead or platform engineer: defines shared workflows, model routing rules, and quality gates for a team.
- Infrastructure engineer: deploys
fabro server start, configures sandboxes and auth, and keeps the system reliable.
Good fits
- small teams comfortable with Git, CLIs, and source-controlled workflow files
- teams that want repeatable automations such as PR review, test generation, or docs sync
Not a fit
- beginners looking for guided product education
- non-technical or no-code users
- users mainly seeking IDE autocomplete or a chat-first coding assistant