Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Diyaz Forge — CRM/ERP Engineering Skill

    1

    Evidence-first engineering playbook for building secure, multi-tenant business software, CRMs, and ERPs.

    Free

    1 useSecurity scanned
    Diyaz Forge — CRM/ERP Engineering Skill

    Diyaz Forge — CRM/ERP Engineering Skill

    Example session with this skill installed

    Add an inventory transfer module to my existing ERP. First inspect the repository and its architecture. Define authorization and stock consistency rules, write tests for duplicate transfers, design secure database migrations, and prepare a safe deployment plan. Do not modify production without my separate approval.

    • Read your context and instructions
    • Compiled the diyaz forge

    Diyaz Forge — Inventory Transfer Module

    SIMULATED EXAMPLE — illustrative implementation plan, not a real repository audit.

    1. Summary

    Goal: Add a warehouse-to-warehouse stock transfer workflow to an existing ERP without compromising stock consistency, tenant isolation, or production stability.

    Status: DESIGN READY · IMPLEMENTATION NOT STARTED · PRODUCTION UNCHANGED

    The agent must inspect the repository, identify existing stock movement models, check authorization boundaries, and reuse established architecture before generating implementation code.

    2. Proposed architecture

    LayerResponsibility
    Domain logicValidate transfer quantities, statuses, and business rules
    Service/APIExecute authenticated transfer commands
    DatabaseAtomically debit the source and credit the destination
    SecurityVerify organization, warehouse, and operator permissions
    UICreate transfer, display status, and prevent duplicate submissions
    TestsVerify invariants, concurrency, and failure paths

    3. Critical business invariants

    1. Transferred quantity must be positive.
    2. Source and destination warehouses must be different.
    3. The operator must be authorized for the relevant warehouses.
    4. The source warehouse must have sufficient available stock.
    5. A transfer must not be posted twice.
    6. A failed transfer must leave both balances unchanged.
    7. The transfer must generate traceable movement records.

    4. Test-first implementation

    Tests must cover

    • Successful transfer between authorized warehouses.
    • Insufficient available inventory.
    • Duplicate request using the same idempotency key.
    • Two concurrent transfers competing for limited stock.
    • Unauthorized cross-tenant transfer.
    • Database failure during posting.
    • Retrying after a network timeout.

    Expected execution sequence

    RED → GREEN → REFACTOR → INTEGRATION TESTS → SECURITY TESTS

    No test is marked PASS until it has actually run.

    5. Safe database changes

    Prepare migrations for transfers, movement records, and unique idempotency constraints.

    Use server-side transactions and enforce authorization through verified identity and database policies. Do not trust warehouse or tenant IDs supplied by the browser.

    Apply compatible changes in stages

    Expand schema → Verify → Deploy application → Observe → Cleanup

    No production migration is executed without separate owner approval.

    6. Release checklist

    CheckStatus
    Repository architecture inspectedNOT RUN
    Domain testsNOT RUN
    Cross-tenant authorization testsNOT RUN
    Concurrent transfer testsNOT RUN
    Migration dry runNOT RUN
    Production deploymentNOT AUTHORIZED

    7. Next steps

    1. Inspect the actual repository and existing inventory tables.
    2. Confirm business rules and authorization requirements.
    3. Implement domain logic and tests.
    4. Prepare the minimum compatible schema changes.
    5. Run validation and present concrete evidence.
    6. Request separate approval before any production operation.

    Diyaz Forge principle: Fast implementation is valuable only when the resulting system is secure, consistent, maintainable, and verifiably correct.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Diyaz Forge v2.1 — From Feature Request to Safe Release

    Diyaz Forge is an engineering playbook for AI coding agents building real-world CRM, ERP, back-office, and multi-tenant SaaS applications.

    Instead of jumping straight into code, it guides AI agents through a structured workflow: repository discovery, architecture, deterministic testing, secure database design, reusable interfaces, and verified releases.

    What it helps you do

    • Build new CRM/ERP applications and extend existing business systems.
    • Design modules with clean business logic, typed services, and reusable UI components.
    • Implement secure PostgreSQL/Supabase authorization and tenant isolation.
    • Prevent silent data truncation using pagination and completeness checks.
    • Protect payments, inventory, and accounting operations against duplicate execution.
    • Plan compatible database migrations with explicit production approval.
    • Create role-focused dashboards and operational interfaces.
    • Verify implementation results with evidence-based checklists.

    What makes it different?

    Diyaz Forge incorporates engineering lessons learned from real business-software projects. It prioritizes safe defaults, minimal changes, independent verification, and clearly documented risks.

    Version 2.1 adds stronger security guardrails, safer migration workflows, structured evaluation scenarios, and generalized architecture patterns.

    Best for: Claude Code, compatible AI coding agents, CRM/ERP developers, SaaS founders, and engineering teams.

    Diyaz Forge is an instructional skill, not an autonomous deployment service or security certification.

    Open source · MIT License · Version 2.1.0

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Prompt & Skill Engineering.

    Requires repository access to inspect files. Does not perform autonomous deployments or actual security certifications. Platform-specific features depend on the host agent capabilities.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    1 use

    Times used to date

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 25 days ago

    • Free with an Agensi account

    Nothing to install. It runs in your AI agent.

    Optional
    GitNode.js 20+

    Permissions

    Terminal / Shell
    Read Files
    Write Files

    Diyaz Forge reads project files, helps write implementation plans, code and tests, and can run local validation commands. Network access, browser access and environment variables are not required for the core skill. Production writes, migrations, deployments and destructive operations require separate explicit owner approval.

    Listed25 days ago

    What's inside

    Frequently Asked Questions

    Diyaz Forge guides AI coding agents to use deny-by-default authorization, PostgreSQL Row-Level Security (RLS), server-side identity verification, and tenant isolation checks. It requires testing unauthorized access scenarios across different users and organizations. These practices help reduce security risks, but the generated implementation still requires testing and security review.

    Diyaz Forge is designed for Claude Code and other AI coding agents that support the SKILL.md format. Its instructions can also be loaded manually in compatible development environments. It is especially useful for React, TypeScript, Supabase, and PostgreSQL projects, but many of its architectural principles apply to other frameworks and backend technologies.

    A standard AI prompt often focuses on generating the requested feature. Diyaz Forge provides a structured engineering workflow: inspect the existing architecture, define business invariants, write deterministic tests, enforce authorization, implement compatible database changes, and verify results before release. It also requires agents to distinguish completed checks from unverified assumptions, reducing the risk of misleading success reports.

    You receive the complete open-source Diyaz Forge v2.1 package, including: The main SKILL.md instructions Nine focused engineering reference guides Secure database and pagination examples Twelve evaluation scenarios Validation scripts and documentation The package is available under the MIT License. No paid subscription or external account is required for its core functionality.

    No. Diyaz Forge is an engineering methodology for AI coding agents, not an autonomous deployment service. It guides implementation, testing, migration planning, and release verification. Production deployments, database migrations, destructive changes, and other consequential actions require separate explicit approval from the project owner.

    Yes. Diyaz Forge is designed for both new applications and existing business systems. It instructs the agent to inspect the current schema, identify dependencies, preserve backward compatibility, test database migrations, and prepare rollback or forward-recovery procedures. Its approach prioritizes minimal, verifiable changes rather than unnecessarily rebuilding working systems.

    New in Prompt & Skill Engineering

    Free