dojocodinglabs

@dojocodinglabs source repo

62 skills
0 followers
16 hours ago last updated

▌
Frontend Dev Guidelines · dojocodinglabs bundle
Frontend development guidelines for Next.js + React 19 + shadcn/ui applications. Modern patterns including App Router, Server Components, Client Components, Server Actions, shadcn/ui with Tailwind CSS, React Hook Form, lazy loading, Suspense boundaries, Supabase client integration, performance optimization, and TypeScript best practices. Use when creating pages, components, forms, styling, data fetching, or working with Next.js/React code.

0
installs
▌
Image Prompting · dojocodinglabs
Best practices for AI image generation prompts with Gemini models. Activated when the user works with nanobanana image generation or editing tools. Provides guidance on prompt structure, style keywords, and iterative refinement.

0
installs
▌
Widget Decomposition · dojocodinglabs
Auto-activates when the user is working on a UI component that needs decomposition into the Atomic Design hierarchy. Works for Flutter widgets and for Vite components (React, Vue, Svelte, Solid, vanilla JS+TS modules with HTML partials). Triggers on: "decompose this widget", "decompose this component", "this widget is too big", "refactor into atoms", "split this into molecules", "extract reusable component", "widget is monolithic", "component is monolithic", "too many responsibilities", "move to core/widgets", "move to src/components", "create atom from this", "Widgetbook entry", "Storybook story", "Histoire story". Do NOT trigger for: design system comparisons (use design-system-analyzer), full codebase audits (use /atomic-design-toolkit:audit command), or non-UI code.

0
installs
▌
Design System Analyzer · dojocodinglabs
Auto-activates when the user discusses design system gap analysis, component catalogs, or cross-referencing their project against a design system. Works for Flutter projects and for Vite projects (React, Vue, Svelte, Solid, vanilla). Triggers on: "design system gap", "component catalog", "what components am I missing", "Material 3 components", "Bootstrap 5 components", "shadcn components", "cross-reference design system", "compare against Carbon", "what widgets does Primer have that I don't", "design token audit", "missing UI primitives". Do NOT trigger for: generating specific feature components (use /atomic-design-toolkit:generate), or general framework development questions.

0
installs
▌
Setup Guide · dojocodinglabs bundle
Knowledge for helping users set up the Remotion Superpowers plugin. Covers API key acquisition, dependency installation, and MCP server troubleshooting. Use when running /setup or when a user has issues with MCP connections.

0
installs
▌
Remotion Production · dojocodinglabs bundle
Full video production workflow for Remotion projects. Teaches how to orchestrate MCP tools (TTS, music, SFX, stock footage, video analysis) into complete Remotion compositions. Use this skill whenever producing a video that needs audio, voiceovers, music, stock footage, or analyzing existing video files.

0
installs
▌
Demo Day Prep · dojocodinglabs
Demo Day preparation workflow — from application write-up (YC, Techstars, etc.) to pitch deck (10-slide standard) to pitch script (3-min standard) to Q&A prep. Produces deck.md, script.md, qa-bank.md, application.md artifacts. Methodology-driven (adapted from YC, Techstars, DojoCoding demo day patterns); standalone — can later consume DojoOS demo day queue via dojoos-api-consumer agent. Use when the user asks "demo day prep", "pitch deck", "pitch script", "demo day application", "accelerator application", "pitch rehearsal", "Q&A prep", "/demo-day-prep".

0
installs
▌
Stage Tracker · dojocodinglabs
Milestone tracking across the 6 DojoOS Launchpad stages (Ideation → Formation → MVP → Traction → Funded → Scaling) with per-stage exit criteria, blockers log, and Dojo-Score-compatible scoring. Produces current-stage.md, milestones.md, blockers.md, dojo-score.md artifacts. Schema-compatible with DojoOS Launchpad stage data model. Use when the user asks "stage tracker", "milestones", "current stage", "startup stage", "Dojo Score", "readiness for next stage", "/stage-tracker". Standalone methodology; syncs with DojoOS via dojoos-api-consumer agent when available.

0
installs
▌
Startup Intake · dojocodinglabs
AI intake interview structured to produce a `startup-profile.md` artifact compatible schema-wise with DojoOS Launchpad Startup Profile. Use when the user asks "startup intake", "startup profile", "onboard my startup", "create startup profile", "AI intake", "/startup-intake". Produces a structured profile covering problem, customer, solution, team, stage, traction, and funding needs — ready for co-founder matching, investor matching, and demo day prep in subsequent skills (or DojoOS Launchpad).

0
installs
▌
Feature To Spike · dojocodinglabs
Transforms methodology learnings from dog-food sessions of launchpad-toolkit into Linear SPIKE issues formatted for William Ugalde (DojoOS Launchpad owner). This is the plugin's DIFFERENTIATOR — the piece that makes launchpad-toolkit a "methodology laboratory" not just a founder tool. Use when the user asks "propose spike", "generate spike", "feature to spike", "productize this", "send to William", "/feature-to-spike".

0
installs
▌
Cap Table Builder · dojocodinglabs
Builds the initial cap table for a single venture in the launchpad stage — founders + employee option pool + advisor pool + convertible instruments (SAFEs, notes) + vesting schedule. Produces `cap-table.md` artifact compatible with Carta/Pulley export formats. Use when the user asks "cap table", "build cap table", "vesting calculator", "SAFE terms", "equity split", "founder equity", "option pool", "/cap-table-builder". LEGAL DISCLAIMER applies — output is preparation aid, NOT legal or tax advice. For multi-venture portfolio cap tables, see sibling plugin `venture-studio-toolkit:cap-table-per-venture`.

0
installs
▌
Founder Documents · dojocodinglabs
Generates the standard founder document stack for a new venture — Founder Stock Purchase Agreement (or Operating Agreement for LLCs), IP Assignment, Vesting Schedule Exhibit, Advisor Agreement (FAST framework), SAFE (post-money YC standard), Term Sheet (Series Seed NVCA standard). Each output is a preparation draft, NOT legal advice. Use when the user asks "founder documents", "founder agreement", "IP assignment", "advisor agreement", "SAFE", "term sheet", "FAST agreement", "/founder-documents". STRONG LEGAL DISCLAIMER applies.

0
installs
▌
Investor Matching · dojocodinglabs
Investor fit scoring methodology. Evaluates investor candidates against a startup profile using a 5-axis framework (stage fit, check size fit, thesis alignment, geography / vertical overlap, value-add depth). Produces ranked target list with customized outreach per investor. Works standalone (manual investor input or curated lists like YC, NVCA directory) — can consume DojoOS investor database via dojoos-api-consumer agent when available. Use when the user asks "investor matching", "find investors", "investor fit", "fundraising targets", "VC list", "angel matching", "/investor-matching". NOT financial or legal advice.

0
installs
▌
Cofounder Matching · dojocodinglabs
Rubric-based co-founder matching methodology. Scores candidate co-founders against a founder's startup profile using a 6-axis framework (domain fit, skill complementarity, values alignment, equity expectations, time commitment, track record). Produces a ranked shortlist with gap analysis + interview questions per candidate. Works standalone (manual candidate input) — can consume DojoOS candidate pool via dojoos-api-consumer agent when available. Use when the user asks "co-founder matching", "find co-founder", "evaluate candidate", "co-founder fit", "co-founder scoring", "/cofounder-matching". NOT legal or HR advice.

0
installs
▌
Premortem · dojocodinglabs
Run a premortem on any plan, launch, product, hire, strategy, or decision. Assumes it already failed 6 months from now and works backward to find every reason why. Produces a revised plan with blind spots exposed. MANDATORY TRIGGERS: "premortem this", "premortem my", "run a premortem", "what could kill this", "future-proof this", "stress test this plan", "what am i missing here", "find the blind spots". STRONG TRIGGERS: "what could go wrong", "am i missing anything", "poke holes in this", "where will this break", "devil's advocate this". Do NOT trigger on simple feedback requests, factual questions, or LLM Council requests. DO trigger when someone has a plan or commitment where the cost of being wrong is high.

0
installs
▌
Prioritize · dojocodinglabs bundle
Applies MoSCoW (bucket) + RICE-adapted (intra-bucket ranking) to Linear issues of a product pillar, traceable to its PIBER+IDCF sub-spike and the latest vision audit. Use when the user asks to "prioritize issues", "priorizar el pillar", "aplicar MoSCoW", "rank the backlog", "RICE scoring", "/prioritize", or wants a data-backed decision on what to work on next within a pillar. Do NOT trigger for: generic backlog ranking without pillar context (use spike-recommend or implement-advisor instead), issue creation, or PR review.

0
installs
▌
Audit Engine · dojocodinglabs
Audit a repo for structural anti-patterns and repo health: schema drift, duplicated logical columns, multiple writers with no owner, and the broader six-family sweep. Use when the user asks to "audit" a repo, hunt for "drift" or an "anti-pattern", check "repo health", or run a named detector profile (e.g. schema-drift / SCH). Owns the full flow: preflight, scope, detect, verify, cure-map, emit (findings doc + OpenSpec change + Bilingual Linear issues + 4-cure scaffold proposals). Do NOT trigger for premortems, code review of a single PR, or generic status reports.

0
installs
▌
Sync Advisor · dojocodinglabs
Measures how far a checkout has drifted from its base ref and routes to the smallest sync that closes the gap — a plain pull, a single-branch rebase, or the team-wide /make-no-mistakes:rebase. Reports which governed files changed, so the answer is "you are missing these three hook fixes", not just "you are N commits behind". Read-only: it measures and recommends, it never syncs. Triggers on: "am I up to date", "is my branch behind", "how far behind am I", "do I need to pull", "is my checkout stale", "what changed on develop", "sync with develop", "sync with release", "post-release sync", "rebase all branches", "team rebase", "my worktrees are behind", "did I miss anything from develop". Does NOT trigger on: interactive rebase ("git rebase -i", "squash these commits"), cherry-pick, resolving a named merge conflict, or a request to actually perform the team sync (that is /make-no-mistakes:rebase itself).

0
installs
▌
Merge Advisor · dojocodinglabs
Computes the ORDER in which a set of open PRs should be merged so that each one is still mergeable when its turn arrives. Measures pairwise file collisions, latent conflicts that only appear after an earlier PR lands, artifacts anchored to a base SHA that every other PR must regenerate, and CI queue capacity. Use when the user asks "in what order do I merge these", "which PR goes first", "how do I avoid conflicts merging all of these", "will merging this break the others", or has a backlog of open PRs against one base. Do NOT trigger for: reviewing a single PR, checking whether one branch is behind (that is sync-advisor), or listing PR status (that is review-open-prs).

0
installs
▌
Spec Recommend · dojocodinglabs bundle
Reads spec files or SRD tasks and produces structured implementation briefs in the Bilingual Format (Human Layer + Agent Layer). Use when the user asks to "analyze this spec", "create an implementation brief", "process this SRD task", "what needs to be built from this spec", or wants to turn a spec document into actionable implementation steps. Supports OpenSpec, numbered steps, and SRD gap audit. Do NOT trigger for: issue analysis (use spike-recommend), code review, or status reports.

0
installs
▌
Review Open Prs · dojocodinglabs
Cross-references open PRs across all repos in the current org with Linear issues, checks Greptile review scores, forces mergeable calculation, and generates an actionable report with merge/rebase/fix recommendations. Use when the user asks "show me open PRs", "what PRs need attention", "review PRs", "check Greptile scores", "what's ready to merge", or wants a comprehensive PR status overview. Do NOT trigger for: creating PRs, code review, or single PR inspection.

0
installs
▌
Spike Recommend · dojocodinglabs
Analyzes issues and produces structured bilingual implementation briefs (Human Layer + Agent Layer). Use when the user asks to "analyze this issue", "create an issue brief", "what does this Linear issue need", pastes a Linear issue URL, or wants to understand and plan work for an issue. By default, the brief is written back to the tracker (Linear / GitHub Issues / etc.) — not to a local file. Do NOT trigger for: general project management or status updates unrelated to a specific issue.

0
installs
▌
Implement Advisor · dojocodinglabs
Detects when the user wants to work on a Linear issue, implement a feature, fix a bug, or start development work. Suggests the /make-no-mistakes:implement command. Triggers on: "implement", "work on issue", "start on", "pick up issue", "Linear issue", "build feature", "fix bug", "start coding", "work on <PREFIX>-NNN" or "implement <PREFIX>-NNN" for any Linear issue prefix (APP, BACK, SEC, MYTEAM, etc. — based on your workspace), "implement this", "let's build", "start implementing", "pick up this ticket", "work on this task", "execute this issue", "develop this feature", "ship this", pastes a Linear issue URL, or provides an issue ID. Does NOT trigger on: rebase, sync branches, standup, test execution, code review, general coding questions, or session management tasks.

0
installs
▌
Review Active Issues · dojocodinglabs
Reviews active Linear issues with GitHub cross-referencing, activity insights, and actionable recommendations. Use when the user asks "what are my active issues", "review my Linear issues", "what's the status of my issues", "show me my backlog", "what issues need attention", or wants a comprehensive view of their Linear workspace. Do NOT trigger for: creating new issues, PR review, or code implementation.

0
installs
▌
Domain Driven Advisor · dojocodinglabs
Guided entry point for repo health when you don't know which audit you need. Use when the user asks "which audit", "where do I start", wants to check "repo health", or mentions "domain driven" design. Inspects the repo, asks a few plain-language questions, recommends which audit(s) to run (or the full ordered sweep), runs them via the audit-engine, and finishes with a premortem on the remediation plan. Best first command for a new repo.

0
installs
▌
Resolve Open Questions · dojocodinglabs
Sweeps the current session for every open question, pending decision, or buried "¿querés que...?" and resolves them through structured AskUserQuestion batches (options + recommendation) instead of prose. Use when the user asks to "resolve open questions", "usemos AskUserQuestion", "/resolve-open-questions", "qué decisiones están pendientes", or when a work session has accumulated multiple unanswered decision points that block execution. Do NOT trigger during active socratic investigation (the user wants evidence + recommendation in prose there), for plan-approval (use ExitPlanMode), or when there is exactly one trivially obvious next step.

0
installs
▌
Code Push · dojocodinglabs
Set up over-the-air (OTA) updates for Flutter apps using Shorebird Code Push. Use this skill when the user asks about hot updates, OTA updates, code push, patching without store review, instant updates, bypassing store releases, Shorebird setup, or deploying Dart code changes without going through the app store submission process. Also triggers on: 'push a fix without store update', 'update without releasing', 'Shorebird', 'patch my app', or 'instant deploy'.

0
installs
▌
Kmp Build · dojocodinglabs
Build, test, and prepare a Kotlin Multiplatform (KMP / KMM) project for shipping to Google Play and Apple App Store. Covers project structure (commonMain, androidMain, iosMain, iosApp/), Gradle Kotlin DSL config, Kotlin/Native compilation, iOS framework integration via CocoaPods or Swift Package Manager, Compose Multiplatform setup, expect/actual patterns, build commands per platform, signing, version sync between Gradle and iOS Info.plist, and common pitfalls (framework size, transitive Kotlin dependencies, kotlinx.* version conflicts). Use this skill when the user asks about KMP, KMM, Kotlin Multiplatform Mobile, shared Kotlin code, Compose Multiplatform, expect/actual, kotlin-multiplatform Gradle plugin, KMP iOS framework, embed Kotlin in iOS, or 'ship a Kotlin Multiplatform app'.

0
installs
▌
Cicd Setup · dojocodinglabs bundle
Set up CI/CD pipelines for Flutter app builds and releases using Codemagic (priority) or GitHub Actions. Use this skill when the user asks about Flutter CI/CD, automated builds, Codemagic setup, GitHub Actions for Flutter, code signing automation, build pipelines, or deploying Flutter apps through CI. Also triggers on: 'automate my builds', 'set up continuous integration', 'pipeline for Flutter', 'codemagic.yaml', 'workflow for Flutter', or any mention of automating Flutter app distribution.

0
installs
▌
Snap Build · dojocodinglabs
Package and publish a Linux desktop application to the Snap Store. Covers snapcraft.yaml authoring (parts, plugs, slots, confinement), build via LXD/Multipass, naming registration on Snap Store, channels strategy (edge/beta/candidate/stable), branch tracks, public/private/unlisted visibility, and CI/CD integration. Use this skill when the user asks about Snap Store, snapcraft, Snapcraft, Ubuntu Store, Linux app distribution, snap publishing, '.snap' files, snap channels, snap confinement, classic snaps, or 'publish to Snap Store'.

0
installs
▌
Launch Plan · dojocodinglabs bundle
Master orchestration for launching a Flutter app to Google Play and App Store in 24 hours. Use this skill when the user wants to ship a Flutter app, plan a mobile release, create a launch timeline, or asks about the steps to publish to app stores. Also triggers when the user mentions 'release plan', 'launch checklist', 'ship my app', 'publish to stores', 'go live', or 'release strategy'. Even if they just say 'I want to launch my app' — this is the skill to use.

0
installs
▌
Pwa Quality · dojocodinglabs bundle
Validate and improve a Progressive Web App's quality before shipping to stores. Covers Web App Manifest schema, service worker patterns (Workbox 7 / offline-plugin / vanilla), Lighthouse PWA audits (the 14 PWA checks), HTTPS + mixed content, install prompts (beforeinstallprompt), iOS-specific quirks (apple-touch-icon, status bar, safe-areas), and common pitfalls that block app store submission. Use this skill when the user asks about PWA readiness, manifest validation, service worker setup, Lighthouse PWA score, Workbox, offline-plugin, install prompts, 'is my PWA ready', 'why does my PWA fail Lighthouse', PWA Builder requirements, or before /ship-pwa runs gate validation.

0
installs
▌
Store Setup · dojocodinglabs bundle
Set up Google Play Console and App Store Connect for a Flutter app. Use this skill when the user needs to create an app in Play Console, set up App Store Connect, configure app metadata, content ratings, pricing, data safety declarations, or any store dashboard configuration. Triggers on: 'create app in Play Console', 'App Store Connect setup', 'configure store', 'data safety form', 'content rating', 'app record', or 'prepare stores for release'.

0
installs
▌
App Security · dojocodinglabs
Configure Firebase App Check and other security measures for Flutter apps before launch. Use this skill when the user asks about App Check, Play Integrity, App Attest, DeviceCheck, API protection, preventing abuse, securing Firebase services, attestation providers, or protecting backend APIs from unauthorized clients. Also triggers on: 'protect my API', 'App Check setup', 'prevent scraping', 'verify legitimate app', or 'secure Firebase'.

0
installs
▌
Monetization · dojocodinglabs bundle
Set up in-app purchases, subscriptions, and payment processing for Flutter apps using RevenueCat or Lemon Squeezy. Use this skill when the user asks about monetization, subscriptions, in-app purchases, paywalls, entitlements, offerings, RevenueCat setup, Lemon Squeezy integration, pricing models, or payment processing for mobile apps. Also triggers on: 'add subscriptions', 'paywall', 'premium features', 'free trial', 'freemium model', or 'how to charge users'.

0
installs
▌
Store Listing · dojocodinglabs bundle
Prepare store listings for Google Play and App Store including screenshots, descriptions, icons, feature graphics, keywords, and ASO (App Store Optimization). Use this skill when the user needs to create or improve store assets, write app descriptions, prepare screenshots, optimize keywords, plan A/B tests for listings, or handle localization. Triggers on: 'store listing', 'app screenshots', 'app description', 'feature graphic', 'ASO', 'keywords', 'store assets', 'app icon specs', or 'localize my listing'.

0
installs
▌
Testing Tracks · dojocodinglabs bundle
Set up and manage app testing tracks across Google Play (internal, closed, open testing), Apple TestFlight (internal, external), and real device testing platforms (BrowserStack, Sauce Labs). Use this skill when the user asks about beta testing, internal testing, TestFlight setup, closed testing, open testing, pre-launch reports, real device testing, QA distribution, tester management, or testing progression before production release. Also triggers on: 'test my app with real users', 'set up beta testing', 'distribute to testers', 'pre-launch report', or 'device lab testing'.

0
installs
▌
Maui Publishing · dojocodinglabs
.NET MAUI multi-target publishing for Android, iOS, Windows (Microsoft Store), and macOS (Mac Catalyst). Covers .NET workload setup, project structure (Platforms/{Android,iOS,Windows,MacCatalyst}), build modes (Debug, Release with AOT/R2R/trimming), per-target signing (Android keystore, iOS provisioning, MSIX self-signing or Microsoft Store, Mac App Store), entitlements, code signing CI workflow, .csproj target framework matrix, MAUI Hot Reload limits in production, and typical migration pitfalls from Xamarin.Forms. Use this skill when the user asks about .NET MAUI, MAUI publishing, dotnet workload install maui, .csproj TargetFrameworks for MAUI, MAUI Android/iOS/Windows packaging, MAUI MSIX, MAUI App Store submission, Xamarin to MAUI migration, or 'ship a .NET MAUI app'.

0
installs
▌
Alt Distribution · dojocodinglabs bundle
Distribute apps through alternative channels beyond mainstream stores. Android: F-Droid, GitHub Releases (Obtainium-compatible), IzzyOnDroid, direct APK. Linux desktop: Flathub (Phase 2). Covers reproducible builds, fdroiddata metadata, AppStream metadata for Flathub, flatpak-builder manifests, and PR workflow to flathub/flathub. Use this skill when the user asks about F-Droid publishing, open source app distribution, APK distribution outside Play Store, Obtainium, reproducible builds, FOSS app stores, fdroiddata, IzzyOnDroid, self-hosted repos, sideloading, distributing without Google Play, Flathub, flatpak, flatpak-builder, AppStream, 'publish to Flathub', or 'Linux desktop FOSS distribution'.

0
installs
▌
Msstore Submission · dojocodinglabs
Submit an app to Microsoft Store via Microsoft Partner Center. Covers two packaging paths (PWA via PWA Builder MSIX, native MSIX from Win32/UWP/desktop apps), Partner Center account setup, app reservation, package upload, store listing requirements (description, screenshots, age rating), certification process (1-7 days typical), and post-launch updates. Use this skill when the user asks about Microsoft Store, Partner Center, MSIX, AppX, Windows Store submission, MS Store certification, Windows app distribution, 'publish to Microsoft Store', or 'Windows app store'.

0
installs
▌
Pre Launch Checklist · dojocodinglabs
Comprehensive pre-launch checklist for Flutter apps covering code quality, environment setup, error monitoring, analytics, force updates, security, store compliance, and production readiness. Based on Andrea Bizzotto's Flutter release methodology. Use this skill when the user asks about release readiness, pre-launch review, production checklist, 'am I ready to launch', 'what am I missing before release', app review preparation, or final checks before submitting to stores. Also triggers on: 'checklist before launch', 'production readiness', 'release preparation', 'review my app before submitting'.

0
installs
▌
New Path · dojocodinglabs
Diálogo guiado para diseñar un Path — una super-estructura SOBRE la capa cmi5-curso que agrupa cursos existentes en milestones ordenados y los envuelve en una credential OpenBadge 3.0. NO modifica ningún course.json (aditivo). Produce path.json (fuente de verdad, validado contra path.schema.json) + content/paths/<slug>/path-overview.md (frontmatter alineado con el contrato dojo-academy). Use when user asks to "create a path", "design a path", "new path", "crear un path", "diseñar un path", "nuevo path", "ruta de aprendizaje", "learning path", "armar un path", "/new-path".

0
installs
▌
New Course · dojocodinglabs
Diálogo guiado para diseñar un curso completo con CONTEXT→CONCEPT→BUILD→SHIP→REFLECT, Builder's Bloom's progression, Ship-First Design, cmi5-ready metadata y Kirkpatrick L1 feedback forms embedded por módulo. Use when user asks to "create a course", "design a course", "new course", "crear un curso", "diseñar un curso", "nuevo curso", "syllabus", "course structure", "armar un curso", "diseñar contenido educativo", "/new-course".

0
installs
▌
Course Diff · dojocodinglabs
Compara dos versiones de un curso (via git tags o commits), clasifica cada cambio, y reporta impacto en alumnos enrolados. Read-only — no modifica state. Use when user asks to "diff course", "compare versions", "comparar versiones", "qué cambió", "/course-diff".

0
installs
▌
Course Audit · dojocodinglabs
Auditoría de curso contra framework completo. Use when user asks to "audit my course", "review my syllabus", "check course quality", "auditar curso", "revisar mi syllabus", "validar curso", "/course-audit".

0
installs
▌
Course Retro · dojocodinglabs
Ingiere xAPI + feedback CSV de una cohorte y produce retro report Kirkpatrick L1-L4 con iteration candidates priorizados (impact × ease). Use when user asks to "course retrospective", "retro", "post-mortem cohort", "Kirkpatrick analysis", "analizar cohort", "retro del curso", "/course-retro".

0
installs
▌
Slide Design · dojocodinglabs
Hormozi-style slide design system for course videos — slide types, accent rules, typography hierarchy, and anti-patterns. Consumer plugins ship the actual HTML/CSS templates referenced here (e.g. dojo-academy ships `content/_templates/slides/dojo-slides-light.html` and `dojo-slides-dark.html`).

0
installs
▌
Course Revise · dojocodinglabs
Aplica cambio incremental a un curso existente: clasifica MAJOR/MINOR/PATCH, valida ID stability, bumpea version, append version_timeline, escribe CHANGELOG entry. Si MAJOR: impact analysis con grandfather clause option. Use when user asks to "revise course", "update course", "bump version", "edit syllabus", "actualizar curso", "iterar curso", "/course-revise".

0
installs
▌
Slides Preview · dojocodinglabs
Renderiza slides Marp por lección desde course.json. Produce .md (Marp source) + .html (rendered deck). Use when user asks to "preview slides", "see slides", "render Marp", "ver slides", "slides preview", "/slides-preview".

0
installs
▌
Blooms Taxonomy · dojocodinglabs bundle
Builder's Bloom's — cognitive scaffolding for course design. Use when planning learning objectives, sequencing modules, writing assessment criteria, designing challenge progression, or reviewing whether a course builds toward higher-order thinking. Activated when discussing cognitive levels, objective writing, or skill progression.

0
installs
▌
Coaching Session · dojocodinglabs
Diseño guiado de sesión de coaching (performance-focused, time-bound, con KPI y withdrawal trigger). Salta detección — el usuario ya declaró tipo. Use when user asks for "coaching session", "sesión de coaching", "/new-coaching-session", o cuando hay performance plan + KPI explícito.

0
installs
▌
Course Visualize · dojocodinglabs
Genera HTML interactivo de un curso para validar Bloom's progression + ship milestones + complexity curve + CONTEXT→...→REFLECT distribution + Kirkpatrick feedback embeds. Use when user asks to "visualize course", "see course curve", "render course HTML", "visualizar curso", "ver Bloom's", "/course-visualize".

0
installs
▌
Teaching Context · dojocodinglabs
Generates and validates per-course teaching-context.md files — defines the target student persona, anxiety points, motivation, and AI positioning for consistent content creation

0
installs
▌
Tutoring Session · dojocodinglabs
Diseño guiado de sesión de tutoría (topic específico, problema-focused, corto plazo, success criterion concreto). Use when user asks for "tutoring session", "sesión de tutoría", "tutor session", "ayuda con [topic]", "/new-tutoring-session", o ayuda puntual con un concepto.

0
installs
▌
Mentoring Session · dojocodinglabs
Diseño guiado de sesión de mentoría (desarrollo integral, larga duración, foco en carrera/identidad/red). Use when user asks for "mentoring session", "sesión de mentoría", "mentor session", "/new-mentoring-session", o relación de mentoring ya establecida.

0
installs
▌
Ship First Design · dojocodinglabs
Ship-First Design — backward design for builders. Use when planning a new course, structuring modules, aligning assessments to objectives, designing challenges, or reviewing whether content connects to ship milestones. Activated when discussing course planning, curriculum design, assessment alignment, or backward design.

0
installs
▌
Workbook Generate · dojocodinglabs
Interactive course workbook design system — turns a course's text classes into one standalone, accessible, interactive HTML explainer (a navigable document chunked by module, Articulate-Rise lesson model; stepped mode for screen-recording). Defines the curated component kit, the content-shape -> component mapping rules, the accessibility contract, and the consumer-spec (instruction-bundle-spec.yaml) consumption + graceful-degrade rules. Consumer plugins own the brand tokens and the component vocabulary via their `workbooks` spec section; this skill stays voice-neutral.

0
installs
▌
Session Plan Audit · dojocodinglabs
Auditoría de plan de sesión 1-on-1 contra framework Irby (2018) coach/mentor/tutor + agenda time-boxing + reflection quality. Use when user asks to "audit my session plan", "review session plan", "auditar sesión", "/session-plan-audit".

0
installs
▌
Learning Evaluation · dojocodinglabs
Learning Evaluation — measuring whether courses actually work. Use when designing post-course surveys, analyzing course metrics, planning retention strategies, reviewing challenge rubrics, or discussing how to measure learning outcomes beyond quiz scores. Reference skill for evaluation planning.

0
installs
▌
Research Methodology · dojocodinglabs bundle
Systematic research methodology for deep-diving into topics, frameworks, and tech stacks before course creation. Defines source quality standards, research artifact formats, and framework extraction criteria.

0
installs
▌
1 On 1 Session Planner · dojocodinglabs
Diálogo guiado para diseñar un plan de sesión 1-on-1 con auto-detect del tipo (coaching/mentoring/tutoring). Use when user asks for "session plan", "1-on-1", "one-on-one", "coaching session", "mentoring session", "tutoring session", "sesión 1-a-1", "plan de sesión", "sesión de coaching", "sesión de mentoría", "sesión de tutoría", "/new-1-on-1-session-plan".

0
installs
▌
Noop Overlay · dojocodinglabs
No-op overlay fixture used to exercise the IDT Base + Overlay discovery contract. Returns the input draft unchanged plus a single demonstration warning string. Use when validating the overlay-protocol runtime, debugging discovery, or when an external-consumer simulation needs an installed-but-inert overlay.

0
installs

62 published skills