Skip to content
OpenSmartRoute
Skillv1.0.0

monorepo-and-tooling

Outlines the monorepo structure and tooling conventions, emphasizing the use of Taskfile.yml, and proper handling of environment variables.

by oimiragieo(0) 0 installs
Free
Sign in to install

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Imported from oimiragieo/agent-studio (.claude/skills/monorepo-and-tooling/SKILL.md). Install upstream with npx skills add oimiragieo/agent-studio --skill monorepo-and-tooling. Copyright stays with the author.

Monorepo And Tooling Skill

  • If using a monorepo structure, place shared code in a packages/ directory and app-specific code in app/.
  • Use Taskfile.yml commands for development, testing, and deployment tasks.
  • Keep environment variables and sensitive data outside of code and access them through .env files or similar configuration.

Iron Laws

  1. ALWAYS place shared code in packages/ and app entry points in app/ — mixing concerns in a flat root structure breaks Turborepo/Nx caching and makes cross-package imports non-deterministic.
  2. NEVER commit .env files or secrets to version control — committed secrets are permanent in history even after deletion; inject secrets at runtime via CI/CD or .env.local (gitignored).
  3. ALWAYS use Taskfile.yml commands for dev, test, and deploy — ad-hoc shell commands in README become stale; Taskfile ensures all contributors run identical commands with consistent flags.
  4. NEVER run build tools directly, bypassing the workspace runner — direct builds skip Turborepo/Nx cache invalidation graphs and produce stale cross-package artifacts.
  5. ALWAYS scope dependency installs to the owning workspace package — installing shared deps in app packages duplicates them in every bundle and breaks workspace deduplication.

Anti-Patterns

Anti-Pattern Why It Fails Correct Approach
Mixing app and shared code in flat root Breaks dependency graph; caching incorrect; circular imports likely Place shared modules in packages/; app entry points in app/; enforce with import rules
Committing .env files Secrets in version history are permanent even after deletion Add .env* to .gitignore; use .env.example for documentation; inject secrets at runtime
Ad-hoc shell commands instead of Taskfile Undocumented; diverges across machines; CI/local parity breaks Define all commands in Taskfile.yml; contributors run task <name>
Running build tools directly, bypassing workspace Bypasses cache graph; produces stale or incorrect cross-package artifacts Always use workspace-level commands (pnpm -w build, nx run, turbo run)
Installing dependencies outside their owning package Duplication in bundles; deduplication breaks; version conflicts between packages Install to the specific package with pnpm add --filter @scope/pkg dep

Memory Protocol (MANDATORY)

Before starting:

cat .claude/context/memory/learnings.md

After completing: Record any new patterns or exceptions discovered.

ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

yaml
targets:
  - https://api.opensmartroute.ai/api/v1/registry/oimiragieo-agent-studio-monorepo-and-tooling/manifest   # or paste the manifest below

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

oimiragieo-agent-studio-monorepo-and-tooling.ocm.jsonjson
{
  "ocm": "1",
  "id": "oimiragieo-agent-studio-monorepo-and-tooling",
  "kind": "skill",
  "name": "monorepo-and-tooling",
  "description": "Outlines the monorepo structure and tooling conventions, emphasizing the use of Taskfile.yml, and proper handling of environment variables.",
  "publisher": "oimiragieo",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "general"
    ],
    "tags": [
      "skill-md",
      "monorepo",
      "turborepo",
      "nx",
      "workspace",
      "tooling",
      "skills-sh"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Outlines the monorepo structure and tooling conventions, emphasizing the use of Taskfile.yml, and proper handling of environment variables."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "skills.sh",
      "repository": "https://github.com/oimiragieo/agent-studio",
      "path": ".claude/skills/monorepo-and-tooling/SKILL.md",
      "ref": "HEAD",
      "url": "https://github.com/oimiragieo/agent-studio/blob/HEAD/.claude/skills/monorepo-and-tooling/SKILL.md",
      "key": "oimiragieo/agent-studio/.claude/skills/monorepo-and-tooling/SKILL.md"
    }
  },
  "instructions": "# Monorepo And Tooling Skill\n\n<identity>\nYou are a coding standards expert specializing in monorepo and tooling.\nYou help developers write better code by applying established guidelines and best practices.\n</identity>\n\n<capabilities>\n- Review code for guideline compliance\n- Suggest improvements based on best practices\n- Explain why certain patterns are preferred\n- Help refactor code to meet standards\n</capabilities>\n\n<instructions>\nWhen reviewing or writing code, apply these guidelines:\n\n- If using a monorepo structure, place shared code in a `packages/` directory and app-specific code in `app",
  "cost": {
    "context_tokens": 974
  }
}

Fetch it by URL: GET /api/v1/registry/oimiragieo-agent-studio-monorepo-and-tooling/manifest?version=1.0.0

Reviews

Star ratings from people who tried it. One review per account; edit yours any time.

No reviews yet. Install it, try it, and be the first to rate it.