project-guardrails

Name: project-guardrails
Availability: InStock
Author: salafidurus

Enforce architectural rules for the Salafi Durus monorepo.

1|Updated Jan 19, 2026

Search Tags:#code quality #architecture #development standards #backend #monorepo #guardrails

Ready to run

npx skills add https://github.com/salafidurus/salafi-audios --skill project-guardrails

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: project-guardrails
Source: https://github.com/salafidurus/salafi-audios/tree/main/.opencode/skills/project-guardrails
Command: npx skills add https://github.com/salafidurus/salafi-audios --skill project-guardrails

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that all development within the Salafi Durus project adheres to strict, non-negotiable architectural guidelines, preventing common pitfalls and maintaining code integrity.

Core Features & Use Cases

Architectural Enforcement: Provides clear, documented rules for backend authority, monorepo boundaries, and app structure.
Dependency Management: Outlines strict rules for dependencies between applications and packages.
Offline & Data Handling: Defines specific requirements for offline functionality and data/media storage.
Use Case: Before starting any new feature development or refactoring, load this Skill to ensure your implementation aligns with the project's core principles, preventing costly rework later.

Quick Start

Use the project-guardrails skill to review the architectural rules before implementing any code changes.

Frequently Asked Questions about project-guardrails

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

FAQPage Schema

How do I enforce development standards for a backend monorepo?▼

You enforce development standards for a backend monorepo by applying strict architectural rules that dictate backend authority, package boundaries, and app structure. This prevents dependency violations and maintains code integrity across the project.

What architectural rules do I need to check before starting feature development?▼

Before feature development, you must check architectural rules covering backend authority, monorepo boundaries, offline functionality, data handling, media storage, API contract generation, and scope control to ensure implementation alignment.

How do I manage dependencies between apps and packages in a monorepo?▼

You manage dependencies between apps and packages in a monorepo by following strict boundary rules that define what applications can depend on which packages. This prevents structural violations and maintains clear separation of concerns.

Does this approach support offline functionality and data handling requirements?▼

Yes, this approach supports offline functionality and data handling by defining specific requirements for offline operations and data/media storage. These rules ensure your implementation meets the project's core architectural principles.

When do I need to review architectural guardrails for code refactoring?▼

You need to review architectural guardrails before starting any code refactoring or new feature development. Loading these rules beforehand ensures your implementation aligns with core principles and prevents costly rework later.

What is the best way to generate API contracts in a structured monorepo?▼

The best way to generate API contracts in a structured monorepo is by following documented architectural rules that enforce backend authority and scope control. This ensures contracts align with the project's non-negotiable guidelines.