mcpField
M
mathodology-project-orientation

mathodology-project-orientation

github.com/sweetcornnaDevelopment316247 installsUpdated today
Repository

About mathodology-project-orientation

A repository-orientation skill for contributors maintaining Mathodology. It explains where source files belong, how to handle installed skills and local mirrors, and which project boundaries to preserve.

Key features

  1. 01Source and documentation locations
  2. 02Skill mirror and backup guidance
  3. 03Repository scope boundaries
  4. 04Optional maintenance checker

Use cases

  1. 01Locate files before editing
  2. 02Back up installed Mathodology skills
  3. 03Avoid adding out-of-scope project components
  4. 04Check repository references and boundaries

MCP support

The README identifies `.mcp.json` as a client configuration for the keyless search MCP and says it is retained in the repository.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sweetcornna/mathodology --skill mathodology-project-orientation

After installing, type/mathodology-project-orientationin Claude Code to confirm it loaded.

Bundled filesagents/openai.yaml

Details

From the project README

Mathodology Repository Orientation

The maintained source is .claude/skills/, with roles in .claude/agents/, workflow prompts in .claude/workflows/, and user documentation in docs/. The root retains AGENTS.md, the two READMEs, LICENSE, .gitignore and .mcp.json.

Skill directories may include reference Markdown, attributed source snapshots, small licensed images, generated demonstration figures and optional scripts. A reference figure is teaching material, not contest evidence. Keep synthetic previews visibly labeled and reproducible. Do not add a dataset collection, application runtime, CI, package manifest or deployment framework.

.agents/skills/ is an ignored local mirror, never a second authoring source. Before replacing this project's installed skills, back up its Mathodology entries outside the checkout. Leave other skills and global directories alone.

.mcp.json is a client configuration for the keyless search MCP. It is retained; custom user configurations and secrets do not belong in source control. Contest output can live in ignored work/ or another working directory. Historical application implementation is available through Git history.

For maintenance, optionally run the repository checker described in maintenance. The checker verifies metadata, references and boundaries; it does not assess mathematical quality.

Comments

Markdown supported