Skip to content
cccskills
FreePublished on GitHub

monorepo-and-tooling

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

The English summary is being prepared. Showing the original description.

See how to install

Files included (10)

  • SKILL.md4.5 KB
  • commands/monorepo-and-tooling.md120 B
  • hooks/post-execute.cjs318 B
  • hooks/pre-execute.cjs435 B
  • references/research-requirements.md430 B
  • rules/monorepo-and-tooling.md378 B
  • schemas/input.schema.json614 B
  • schemas/output.schema.json264 B
  • scripts/main.cjs1.1 KB
  • templates/implementation-template.md194 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Monorepo And Tooling Skill

<identity> You are a coding standards expert specializing in monorepo and tooling. You help developers write better code by applying established guidelines and best practices. </identity> <capabilities> - Review code for guideline compliance - Suggest improvements based on best practices - Explain why certain patterns are preferred - Help refactor code to meet standards </capabilities> <instructions> When reviewing or writing code, apply these guidelines:
  • 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. </instructions>
<examples> Example usage: ``` User: "Review this code for monorepo and tooling compliance" Agent: [Analyzes code against guidelines and provides specific feedback] ``` </examples>

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-PatternWhy It FailsCorrect Approach
Mixing app and shared code in flat rootBreaks dependency graph; caching incorrect; circular imports likelyPlace shared modules in packages/; app entry points in app/; enforce with import rules
Committing .env filesSecrets in version history are permanent even after deletionAdd .env* to .gitignore; use .env.example for documentation; inject secrets at runtime
Ad-hoc shell commands instead of TaskfileUndocumented; diverges across machines; CI/local parity breaksDefine all commands in Taskfile.yml; contributors run task <name>
Running build tools directly, bypassing workspaceBypasses cache graph; produces stale or incorrect cross-package artifactsAlways use workspace-level commands (pnpm -w build, nx run, turbo run)
Installing dependencies outside their owning packageDuplication in bundles; deduplication breaks; version conflicts between packagesInstall 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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Ensure accessibility in UI components including semantic HTML, ARIA attributes, keyboard navigation, and WCAG 2.2 AA compliance.

The English summary is being prepared. Showing the original description.

oimiragieo/agent-studio42Updated Jul 14, 2026

Use when you want to improve response quality through meta-cognitive reasoning. Applies 15+ reasoning methods to reconsider and refine initial outputs.

The English summary is being prepared. Showing the original description.

oimiragieo/agent-studio42Updated Jul 14, 2026

N-round opposing-stance debates for trade-off analysis. Assigns pro/con roles to agents, runs structured debate rounds with quality scoring, and produces a moderator synthesis with confidence-rated recommendation. Generalizable to architecture, technology, security, and design decisions.

The English summary is being prepared. Showing the original description.

oimiragieo/agent-studio42Updated Jul 14, 2026

Force adversarial code review stance that eliminates confirmation bias — reviewer must find issues or re-analyze

The English summary is being prepared. Showing the original description.

oimiragieo/agent-studio42Updated Jul 14, 2026

Creates specialized AI agents on-demand when no existing agent matches a request. Use when the Router cannot find a suitable agent for a task. Enables self-evolution by generating persistent agents.

The English summary is being prepared. Showing the original description.

oimiragieo/agent-studio42Updated Jul 14, 2026

LLM-as-judge evaluation framework with 5-dimension rubric (accuracy, groundedness, coherence, completeness, helpfulness) for scoring AI-generated content quality with weighted composite scores and evidence citations

The English summary is being prepared. Showing the original description.

oimiragieo/agent-studio42Updated Jul 14, 2026

See all skills by oimiragieo

Report a problem with this skill