Development

Family index for authoring Open edX courses directly on Studio (studio.learn.iblai.app) and verifying them on the LMS (lms.ibl.ai) from the terminal — preflight, build order, how to plan a production-grade outline, the bulk outline builder versus block-by-block calls, and which /iblai-api-studio-* skill covers sign-in, course create, sections/subsections/units, HTML/PDF/problem components, settings, team, grading, publish and LMS-side checks. Use when the user says Studio, Open edX, edX, xblo...

Manage units (vertical blocks) of an Open edX course on Studio — create a unit inside a subsection, list and reorder the components it contains, rename, set staff-only visibility, duplicate, move between subsections, and delete. Use when the user says unit, page, "add a page to the lesson", reorder components, or asks what is inside a unit. Session auth via studio.env; components themselves are added with the html / problem / pdf skills. For the build order and the other Studio skills, see /i...

Read and update an Open edX course's settings on Studio — schedule (start, end, enrollment dates), pacing, language, title/subtitle/description/short description/overview (about page), effort, intro video, course and banner images (asset upload), catalog fields that flow to the ibl.ai LMS app (subject, tags, level, topics, promotion, slug, agent), plus advanced settings such as advanced_modules — and the ordering rules (settings before content, pacing before the course starts, enrollment befo...

Manage the top level of an Open edX course outline on Studio — create sections (chapter blocks) under the course root, rename them, set release dates and staff-only visibility, reorder them, read the whole outline with publish state, and delete sections. Use when the user says section, week, module, chapter, course outline, "hide this from users", or reorder. Session auth via studio.env. For the build order and the other Studio skills, see /iblai-api-studio.

Publish draft changes of an Open edX course on Studio — make a unit, subsection, section or the whole course public, read the publish and visibility state of every block (published, has_changes, visibility_state), discard unpublished changes, and confirm users can now see the content; includes the first-publish checklist (settings, pacing, enrollment window, complete outline). Use when the user says publish, go live, release, "users can't see", draft vs published, discard changes, or asks whe...

Add and edit problem (assessment) components in an Open edX unit on Studio — create ONE problem block per unit that holds all of the unit's questions as several OLX responses, write the OLX in data, set display name, max attempts, weight, show-answer and randomization in metadata, and clear the stale markdown so the OLX is authoritative. Ships verified OLX for multiple choice, checkboxes, numerical, text and dropdown questions with hints and solutions. Use when the user wants a quiz, question...

Add a PDF viewer component to an Open edX unit on Studio — enable the pdf advanced module on the course, upload the PDF as a course asset, create the pdf block, and save its title and href through the block's own save_pdf handler (the generic xblock update does not persist the file field). Use when the user wants a PDF, slides, a syllabus, a reading handout or any document displayed inline in a unit. Session auth via studio.env.

Build or bulk-edit an Open edX course outline on Studio — a new course in one request from a JSON spec via the IBL course-creator API (POST /api/v1/ibl/course/create_full_course, which also publishes), or an existing course at scale with the bundled reconcile driver that diffs the same spec against the live outline and creates/updates/reorders/deletes idempotently; plus the v1 helpers to list every unit with its components and create/update/publish single blocks. Use when a course plan is kno...

Verify and operate the LMS side of an Open edX course built on Studio — the calls the lms.ibl.ai LMS app makes against the LMS API: enroll yourself or (as course staff) other users, check enrollment status, list a course's users, read the published outline and blocks as a user, read course details and the merged course metadata the catalog shows, and progress/grading as seen by users. Use after publishing to confirm what users see, to enroll test users, or when the user asks "is it in the cat...

Add and edit HTML (text) components in an Open edX unit on Studio — create the html block, write its HTML body and title in one update, reference uploaded images and files via /static/ paths, duplicate or delete it, and follow the authoring rules that make content look designed (cards, callouts, tables, tooltips via inline CSS) while leaving typography and page width to the LMS. Use when the user wants text, a reading, an explanation, a callout, a comparison table, an embedded video/iframe, o...

Create a course on Open edX Studio (studio.learn.iblai.app) from the terminal — POST the org key and display name (optionally number and run) to Studio's course-management endpoint and get the course key back; list the user's courses, read a course summary, derive the course root block for outline work, and delete a course. Use when the user wants a new Open edX course, asks for their course key, needs to know which courses they can edit, or wants a course removed. Session auth via studio.env...

Sign in to Open edX Studio (studio.learn.iblai.app) and the LMS from a browser window the user controls, capture the session cookies (studio_session_id, sessionid, csrftoken) with the bundled Playwright script, verify them, and write the gitignored studio.env that every /iblai-api-studio-* skill reads; --check validates an existing session in one command. Use first whenever the user wants to author or configure an Open edX course from the terminal, and again when a Studio call answers 302 to ...

Manage an ibl.ai organization's learning catalog via the platform API — courses, programs, pathways, resources, skills, roles, course/program metadata, plus enrollment, eligibility checks, catalog search, and course reviews. Org-wide content and enrollment operations. Use when wiring up the catalog, enrolling users, checking eligibility, or curating skills/roles/pathways.

Build and populate Canvas LMS courses through the Canvas REST API — creating course shells, modules and module items, pages, assignments, quizzes (Classic and New Quizzes), discussions, announcements, files, assignment groups, sections and enrollments, plus bulk seeding from a spec file, course copies and Common Cartridge imports. Use this skill whenever the user mentions Canvas, Instructure, canvas.instructure.com, a Canvas API token, `/api/v1/courses`, or asks to script, seed, migrate, bulk...

Decide how money works for an ibl.ai app — how your organization is charged (prepaid credits, plans, auto-recharge, your own LLM keys, spend caps) and which of the three rails to use to charge your own users (platform credits, an app paywall on your own Stripe key, or item-level monetization via Stripe Connect). Use when the user mentions pricing, charging users, paywall, subscription, credits, "how do I get paid", Stripe, spend limits, budgets, or LLM cost. For the credit widget see /iblai-v...

Add the OS app's Code mode to a vibe Next.js + Tauri app — a "Code" pill in the chat composer that turns the agent into an agentic coding tool (opencode over ACP) editing files, running commands, and committing in a workspace on the user's machine, with per-operation Allow/Deny permission cards, a loopback proxy that never hands the agent the real token, per-agent skills synced from the platform, and phone access by pairing a mobile build to a desktop. Ships the Tauri Rust modules from src-ta...

MCP connectors for ibl.ai agents, end to end — register MCP servers (featured cross-organization sharing, enable/disable, OAuth service linkage), manage credential connections with the auth_type × scope matrix (org / agent / per-user), wire servers onto an agent, run the OAuth connected-service lifecycle, handle per-user in-chat OAuth (the oauth_required / oauth_connection_resolved chat events), and debug MCP auth failures (401s, missing OAuth prompts, agents ignoring servers). Use when wirin...

Safely manage registered project environment variables through Kavranta's redacted local broker. Use for `.env` or Wrangler `.dev.vars` inspection and edits, groups, access policies, links, value-hidden generation or reuse, deployment and comparison, encrypted team sharing, and Provider or Action Packs. 한국어로 “환경변수 관리·정리”, “.env를 값 없이 확인”, “키 연결·재사용”, “환경변수 올리기”, “카브란타로 처리”를 요청할 때도 사용한다.

Establish Specs from an explicitly selected existing implementation, then retire this temporary adoption Skill after successful finalization.

Status: Accepted Supersedes the `sb-discovery` ownership and routing portions of Decisions [0181](./0181-reverse-spec-establishment.md), [0188](./0188-retire-legacy-staged-adoption.md), [0191](./0191-resumable-reverse-establishment.md), and [0192](./0192-typed-milestone-action-handlers.md), and [0193](./0193-progressive-discovery-procedures.md). Their fixed-evidence, confirmation, lifecycle, resume, and non-release finalization contracts remain authoritative.

Review and integrate Dependabot pull requests in Huruikagi/specbind one at a time, with current-branch checks, main CI verification, and affected dependency or toolchain validation. Use when asked to handle or merge SpecBind Dependabot PRs; do not use for dependency upgrades that have no Dependabot PR.

MANDATORY for every coding agent and contributor touching localized content — keep all five localization surfaces (dashboard UI keys, wiki page, mirrored READMEs, locale-aware formatting, language switchers) in parity across every supported language. Use automatically (without being asked) whenever you add or change user-visible UI copy, add an i18n key, edit README.md, edit wiki/index.html, or change docs that the READMEs and wiki mirror — and use the full new-language checklist whenever add...

MANDATORY for every coding agent and contributor touching localized content — keep all five localization surfaces (dashboard UI keys, wiki page, mirrored READMEs, locale-aware formatting, language switchers) in parity across every supported language. Use automatically (without being asked) whenever you add or change user-visible UI copy, add an i18n key, edit README.md, edit wiki/index.html, or change docs that the READMEs and wiki mirror — and use the full new-language checklist whenever add...

MANDATORY for every coding agent and contributor touching localized content — keep all five localization surfaces (dashboard UI keys, wiki page, mirrored READMEs, locale-aware formatting, language switchers) in parity across every supported language. Use automatically (without being asked) whenever you add or change user-visible UI copy, add an i18n key, edit README.md, edit wiki/index.html, or change docs that the READMEs and wiki mirror — and use the full new-language checklist whenever add...