What problem does it solve?
This Skill solves the problem of quickly understanding StudySolo’s real architecture and operational boundaries so you can contribute or navigate the repo without repeatedly hunting through docs and code.
Core Features & Use Cases
- Repository map & ownership boundaries: Clarifies where frontend, backend, shared submodules, docs, scripts, and project-level skills live, including git submodule vs subtree sync semantics.
- Technology stack & structure navigation: Lists the main framework/library versions and the key directories for both frontend and backend so you can locate authoritative sources fast.
- API grouping & workflow node taxonomy: Provides a fast route list for API domains and an up-to-date inventory of workflow node types, states, and edge types used by the DAG execution engine.
- AI catalog/usage/admin domain rules: Defines the model routing and billing-related concepts (e.g., selected_model_key, sku_id, routing_policy, and unified *cny fields) to prevent mismatches when modifying AI behavior.
- Documentation quality guardrails: Enforces “source-of-truth” rules (configs/models/migrations/code over README) and consistent doc encoding/linting expectations.
Quick Start
Use the project-context skill to orient yourself before changing any workflow nodes, AI routing/catalog logic, API endpoints, or shared/submodule-related documentation in the StudySolo repository.