Skip to content

matlab/agent-skills-playground / demos/mbse-with-agentic-ai/skills/matlab-project

matlab-project

Verified

Use this skill for any work involving a MATLAB Project (.prj file) — creating a new project, tracking files, managing the project path, configuring Simulink cache and code-generation folders, running project health checks, or writing build scripts that keep the project in sync with the file system. Trigger phrases include "set up a MATLAB project", "create a .prj", "track this file in the project", "project health check", "build script conventions". This skill is the generic foundation; domain-specific skills (e.g. `mbse-workflow`) build on it.

FileKindSize
SKILL.mdskill md9.3 KB
code/registerWithProject.mother1.0 KB
code/setupProject.mother2.7 KB
templates/decisions.mdmarkdown1.3 KB
templates/plan.mdmarkdown1.3 KB

templates/decisions.md

View on GitHub
# {{ProjectName}} — Decision Log

Append-only log of non-obvious design decisions made while building this project. Each entry captures enough context that a future reader — another engineer, another Claude session — can understand *why* a choice was made without reverse-engineering the code.

## Format

Each entry follows this shape:

    ## YYYY-MM-DD — <milestone or phase> — <short decision title>
    **Context:** Why this decision point came up; what prompted the choice.
    **Options considered:** A / B / C (omit if only one was seriously on the table)
    **Chosen:** <selected option>
    **Rationale:** Tradeoff that settled it, or the stakeholder preference that drove it.
    **Revisit if:** Condition under which this decision should be reopened.

## When to append

- At any checkpoint where the selected approach **was not forced by the requirements** — naming conventions, decomposition granularity, scope trims, etc.
- When work **rolls back or redirects** — record both the original choice and the reason for the change. Don't silently overwrite earlier entries; add a new one.
- When scope expands or contracts mid-project.

Skip entries for:
- Mechanical steps (e.g. "created the .prj file")
- Decisions fully determined by the inputs (no judgment was required)
- Bug fixes or API-level iteration (those go in commit messages, not decisions)
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall