splent

SPLENT framework architecture and conventions — the canonical reference for working in a SPLENT codebase. Consult this whenever you are reading, writing, or reviewing SPLENT code such as features, products, blueprints, services, repositories, models, routes, template hooks, the service locator, per-feature Alembic migrations, the feature contract in pyproject.toml, the SPL/UVL variability model, or the splent CLI. Use it before writing any feature/product code so it follows the real patterns instead of generic Flask. Triggers on mentions of splent, splent_feature_*, splent_io, feature:create, product:derive, BaseService/BaseRepository, UVL, SPL, or work inside splent_cli/splent_framework/splent_catalog.

Diagnose and fix problems in a SPLENT workspace. Use whenever something is broken or behaving oddly — product:derive or product:up fails, the app won't start, a UVL model is unsatisfiable, migrations fail or the DB is out of sync, features are missing or won't import, symlinks/cache are broken, env vars or Docker/infra are misconfigured, or doctor/product:validate report errors. Triggers on error output, "it's broken", "won't start", "derive failed", "migration error", "feature not found", "UVL unsatisfiable", or any SPLENT troubleshooting request.

Author a SPLENT feature end-to-end. Use whenever the user wants to build, add, scaffold, or extend a feature in a SPLENT workspace — from a plain description like "add a notes feature with title and body owned by the user" all the way to working code. It will scaffold with feature:create, write models/repositories/services/routes/templates/hooks and tests following SPLENT conventions, add it to the SPL, install it into the product, run migrations, and verify. Triggers on "new feature", "add a feature", splent_feature_*, feature:create, or any request to implement domain functionality in a SPLENT product.

Set up, configure, run, and onboard a SPLENT product. Use whenever the user wants to create a new product, choose its features, derive/build/start it, seed the database, get it running locally, or onboard an existing product after cloning the workspace. Handles the full pipeline (create → select → configure → resolve → derive → seed → run) and day-to-day ops (up/down/restart/logs/console/routes), picking the right path from the current state. Triggers on "set up the product", "run the app", "get it running", "configure features", product:create, product:derive, product:up, or a fresh-clone onboarding.