skills.rest
ogc-maps
ogc-mapsOFFICIAL
Explore all skills by this author →
GitHub

project-conventions

Document and enforce monorepo architectural rules via CLAUDE.md and .cursorrules.

2|Updated Feb 17, 2026
Search Tags:#architecture#monorepo#guidelines#quality-assurance#coding-standards#pr-review
One-click install
npx skills add https://github.com/ogc-maps/storybook-components --skill project-conventions-ogc-maps
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-conventions
Source: https://github.com/ogc-maps/storybook-components/tree/main/.claude/skills/project-conventions
Command: npx skills add https://github.com/ogc-maps/storybook-components --skill project-conventions-ogc-maps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The non-negotiable architectural rules prevent drift in the storybook-components / ogc-maps monorepo by codifying the preferred structure, safeguards, and reasoning that guide every non-trivial change.

Core Features & Use Cases

  • Documentation of rules: A centralized, AI-friendly guide detailing why each rule exists and when it applies.
  • Early guardrails: Quick-reference checks to ensure changes align with the repository's conventions at the start of a task or PR.
  • Consistency across tasks: Helps engineers decide where code should live (lib vs app), how data flows, and how interfaces should be shaped.

Quick Start

Read this guide before implementing any non-trivial change to the codebase to ensure alignment with the architecture rules.

Frequently Asked Questions about project-conventions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce coding standards and architecture rules in a monorepo?▼

You can enforce architecture rules in a monorepo by codifying structural guardrails in CLAUDE.md and .cursorrules files, ensuring every non-trivial code change aligns with established conventions before a PR.

Why does monorepo architecture drift occur and how can I prevent it?▼

Architecture drift occurs when code changes bypass structural guidelines. Prevent drift by applying a schema-driven approach with centralized, AI-friendly documentation dictating where components, hooks, and stores must live.

What is the best way to standardize code structure across multiple packages?▼

The best way to standardize code structure is using a centralized guide detailing why each rule exists, applying early guardrail checks at the start of a task to align changes with repository conventions.

Do I need a schema-driven approach for PR reviews in a monorepo?▼

Yes, a schema-driven approach is necessary for PR reviews to reduce brittle integrations. It validates code changes against documented architectural rules to maintain consistency across packages.

Can I use CLAUDE.md and .cursorrules for quality assurance and coding standards?▼

Yes, you can use CLAUDE.md and .cursorrules for quality assurance by defining a schema-driven approach that provides reusable rationale and guardrails for significant code changes across packages.

When should I apply architectural guardrails during software engineering tasks?▼

Apply architectural guardrails at the start of any task or PR involving significant changes to components, hooks, stores, routes, or configuration to ensure alignment and prevent architectural drift.

Related Skills

Explore More Software Engineering Skills→
DIO0550DIO0550

rules-setup

Adds d-market rule-based skill usage guidelines to TypeScript/React project instruction files.

Community
Basic
DanielPodolskyDanielPodolsky
274

database-fundamentals

Analyze database schema design, SQL queries, and ORM usage for correctness.

Community
Basic
MatthieuszMatthieusz

coding-standards

Validate TypeScript code against predefined coding standards using static analysis tools.

Community
Advanced
SergeiGolosSergeiGolos
1

documentation-templates

Provide standardized templates for READMEs, API references, and changelogs.

Community
Basic