creatyss-core

Enforce project-specific guardrails and execution posture for Creatyss development.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Deadpool042/Creatyss --skill creatyss-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: creatyss-core
Source: https://github.com/Deadpool042/Creatyss/tree/main/.agents/skills/creatyss-core
Command: npx skills add https://github.com/Deadpool042/Creatyss --skill creatyss-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill codifies the absolute guardrails, execution posture, and non-negotiable priorities that guide all Creatyss work, reducing drift and misalignment.

Core Features & Use Cases

  • Enforces repository doctrine and project constraints across engineering tasks, reviews, and deployments.
  • Provides a consistent decision framework to avoid unnecessary architectural drift and scope creep.
  • Use Case: When evaluating a change, refer to the canonical doctrine to determine alignment with project constraints before coding.

Quick Start

Apply the repository's canonical doctrine to every decision and action in Creatyss projects.

Frequently Asked Questions about creatyss-core

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

FAQPage Schema
How do I enforce strict TypeScript and Next.js App Router guardrails across a repository?

You can enforce strict TypeScript and Next.js App Router guardrails by applying canonical doctrine documents to every engineering decision, ensuring code, tests, and deployments align with non-negotiable project constraints before execution.

What are execution posture guardrails in software engineering?

Execution posture guardrails in software engineering are non-negotiable constraints and a clear decision hierarchy that guide development tasks, preventing architectural drift and scope creep across code, tests, and deployments.

How do I prevent architectural drift and scope creep in PostgreSQL and Docker Compose projects?

Prevent architectural drift and scope creep by codifying absolute project priorities and constraints into a canonical doctrine, referencing it to determine alignment before writing code or evaluating changes.

Can I use a decision framework to standardize reviews and deployments for Next.js App Router?

Yes, you can use a codified decision framework to standardize reviews and deployments for Next.js App Router, applying repository doctrine to maintain consistent, maintainable delivery across all development tasks.

When do I need a canonical doctrine for TypeScript project execution?

You need a canonical doctrine for TypeScript project execution when you want to reduce drift and misalignment, ensuring all developers follow non-negotiable constraints spanning PostgreSQL, Docker Compose, and strict typing.

Does applying non-negotiable constraints limit flexibility in software engineering tasks?

Applying non-negotiable constraints limits flexibility intentionally to ensure consistent, maintainable delivery, guiding decisions from doctrine documents to code while preventing unnecessary architectural drift and scope creep.