project-context

Map the StudySolo repository structure, tech stack, and workflow node taxonomy.

3|2|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/AIMFllys/StudySolo --skill project-context-aimfllys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-context
Source: https://github.com/AIMFllys/StudySolo/tree/main/docs/issues/TeamRefactor/codex-analysis/01-baseline/skills/project-context
Command: npx skills add https://github.com/AIMFllys/StudySolo --skill project-context-aimfllys

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about project-context

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I navigate the StudySolo repository architecture before modifying workflow nodes?

To map StudySolo repository boundaries, identify frontend, backend, shared submodules, and docs directories. This clarifies ownership boundaries and git subtree sync semantics before you modify workflow nodes or API endpoints.

What is the workflow node taxonomy and state definition in the DAG execution engine?

The workflow node taxonomy defines node types, states, and edge types used by the DAG execution engine. Reviewing this inventory ensures modifications remain consistent with the actual codebase.

How do I manage AI catalog routing and billing concepts like routing_policy and sku_id?

Managing AI catalog routing requires defining selected_model_key, sku_id, routing_policy, and unified cny fields. These domain rules prevent mismatches when modifying AI behavior and billing logic.

What are the documentation source-of-truth rules for API domain grouping?

Documentation source-of-truth rules prioritize configs, models, migrations, and code over README files. Enforcing these guardrails ensures API domain grouping and encoding remain consistent with the actual codebase.

Does the StudySolo platform use Supabase for frontend and backend shared boundaries?

Yes, StudySolo uses Supabase across frontend, backend, and shared boundaries. Repository context mapping clarifies tech-stack versions and key directories to locate authoritative sources for Supabase integrations.