oimpresso-stack

Load canonical oimpresso ERP stack rules and guardrails before starting work.

Updated May 14, 2024
One-click install
npx skills add https://github.com/wagnerra23/oimpresso.com --skill oimpresso-stack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oimpresso-stack
Source: https://github.com/wagnerra23/oimpresso.com/tree/main/.claude/skills/oimpresso-stack
Command: npx skills add https://github.com/wagnerra23/oimpresso.com --skill oimpresso-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates repeated reading and re-alignment on the oimpresso canonical stack rules, so you can start work inside the ERP faster and implement modules consistently.

Core Features & Use Cases

  • Onboarding primer loader: Quickly applies the agreed stack baseline (Laravel 13.6, PHP 8.4, Inertia v3, multi-tenant rules, and UltimatePOS modular pattern) to your current task.
  • Module implementation guardrails: Enforces essential constraints such as mandatory business_id scoping, append-only rules for legal domains, and “imitate reference modules” guidance before changing structures.
  • Architecture consistency for AI-assisted work: Aligns new module edits and IA-related workflows with the documented ADR-driven “stack-alvo” (laravel/ai layering, MCP server setup, and tooling expectations).

Notes

Best fit when you are entering a new module, starting a task, or preparing to change code in a way that must remain compatible with the established oimpresso architecture.

Quick Start

Use the oimpresso-stack skill to align your changes with the canonical ERP stack rules before modifying any code in your target module.

Frequently Asked Questions about oimpresso-stack

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

FAQPage Schema
How do I enforce multi-tenant scoping with a mandatory business_id in a Laravel ERP module?

To enforce multi-tenant scoping with a mandatory business_id, apply the canonical stack guardrails before modifying code. This ensures all module changes adhere to oimpresso's mandatory business_id scoping rules.

What are the guardrails for implementing append-only legal protections in a multi-tenant architecture?

Append-only legal protections in a multi-tenant architecture require adhering to canonical stack constraints that prevent destructive updates to legal domains. This Skill enforces those append-only rules during module implementation.

How do I align new Laravel module edits with ADR-driven architecture constraints?

Aligning new Laravel module edits with ADR-driven architecture constraints involves loading the canonical stack primer. This applies documented layering, MCP server setup, and tooling expectations to your AI-assisted workflows.

Does the oimpresso-stack skill support onboarding to the UltimatePOS modular pattern?

Yes, the oimpresso-stack skill supports onboarding to the UltimatePOS modular pattern. It loads the agreed stack baseline including Laravel, PHP, Inertia, and the modular pattern to standardize implementation.

Why do I need to imitate reference modules before changing structures in a multi-tenant ERP?

You need to imitate reference modules before changing structures to maintain architecture consistency across the ERP. This guardrail prevents structural drift and ensures new code matches established modular patterns.

What is the best way to start implementing a new module in the oimpresso ERP?

The best way to start implementing a new module in the oimpresso ERP is to load the canonical stack primer first. This aligns your changes with stack rules, multi-tenant scoping, and ADR constraints before you modify any code.