ai-ops-cli 0.1.8 → 0.1.10

package/data/rules/nextjs.yaml

@@ -0,0 +1,34 @@
+id: nextjs
+category: framework
+tags:
+  - typescript
+  - react
+  - nextjs
+  - app-router
+priority: 50
+content:
+  constraints:
+    - "DO NOT import server-only code into Client Components. Enforce with 'server-only'."
+    - 'DO NOT store secrets in NEXT_PUBLIC_ variables. Only NEXT_PUBLIC_ vars are exposed to the browser bundle.'
+    - 'DO NOT use next/router in App Router projects. Use next/navigation APIs.'
+  guidelines:
+    - 'Follow App Router file conventions (page.tsx, layout.tsx, loading.tsx, error.tsx, not-found.tsx).'
+    - "Keep Server Actions in dedicated files (e.g., actions.ts) with 'use server'."
+    - 'Use next/image with explicit dimensions or fill + sizes.'
+    - 'Use next/font in root layout and apply through CSS variables.'
+    - 'Use middleware.ts only for cross-cutting concerns (auth redirect, locale, header policy).'
+    - 'Export metadata (or generateMetadata) for public pages with title/description/OpenGraph.'
+    - 'Add JSON-LD structured data for public pages when SEO/GEO matters.'
+  decision_table:
+    - when: 'A component needs browser APIs, state hooks, or event handlers'
+      then: "Add 'use client' at the smallest leaf component"
+      avoid: "Marking high-level parent trees as 'use client'"
+    - when: 'Page data is needed for initial render'
+      then: 'Fetch in Server Components with async/await'
+      avoid: 'Client-side useEffect fetch for primary page data'
+    - when: 'Internal form mutation is needed'
+      then: 'Use Server Actions'
+      avoid: 'route.ts endpoints for simple internal form writes'
+    - when: 'External API/webhook endpoint is needed'
+      then: 'Use route.ts with explicit HTTP method exports'
+      avoid: 'Server Actions for public API integration points'

package/data/rules/plan-mode.yaml

@@ -0,0 +1,30 @@
+id: plan-mode
+category: standard
+tags:
+  - general
+  - planning
+  - mermaid
+priority: 71
+content:
+  constraints:
+    - 'DO NOT mix Mermaid diagram types arbitrarily. Pick the type that matches the information structure.'
+  guidelines:
+    - 'Prefer Mermaid diagrams over long bullet lists when explaining flow, sequence, state, or structure.'
+    - 'Use flowchart for UX/control flows and decision trees.'
+    - 'Use sequenceDiagram for request/response and service interaction flows.'
+    - 'Use erDiagram for entities and schema relationships.'
+    - 'Use stateDiagram-v2 for lifecycle/state transitions.'
+    - 'Wrap diagrams in fenced ```mermaid code blocks.'
+  decision_table:
+    - when: 'Describing user journey or UI navigation'
+      then: 'Use flowchart (LR or TD)'
+      avoid: 'Text-only step lists'
+    - when: 'Describing API or service interactions'
+      then: 'Use sequenceDiagram'
+      avoid: 'Plain text arrows only'
+    - when: 'Describing schema relationships'
+      then: 'Use erDiagram'
+      avoid: 'Unstructured table bullet lists'
+    - when: 'Describing state transitions'
+      then: 'Use stateDiagram-v2'
+      avoid: 'Flat textual state lists'

package/data/rules/prisma-postgresql.yaml

@@ -0,0 +1,30 @@
+id: prisma-postgresql
+category: database
+tags:
+  - typescript
+  - prisma
+  - postgresql
+priority: 40
+content:
+  constraints:
+    - 'DO NOT interpolate strings in $queryRawUnsafe. Use $queryRaw tagged templates or parameterized placeholders.'
+    - 'DO NOT return Prisma models directly from APIs. Use select or DTO mapping to avoid leaking sensitive fields.'
+    - 'DO NOT define mutable models without updatedAt DateTime @updatedAt.'
+    - 'DO NOT use $use() middleware. Use Client Extensions ($extends) in Prisma v7+.'
+    - 'DO NOT use prisma db push in production. Use prisma migrate deploy with versioned migrations.'
+  guidelines:
+    - 'Use generator client { provider = "prisma-client"; output = "./generated/prisma/client" }.'
+    - 'Use @prisma/adapter-pg and set explicit pool/timeout values for your environment.'
+    - 'Add indexes for frequent where/orderBy/join patterns, including composite indexes where needed.'
+    - 'Set explicit timeout and maxWait for interactive transactions.'
+    - 'Centralize datasource and migration settings in prisma.config.ts.'
+    - 'Implement soft delete with a Client Extension query hook that injects deletedAt: null filtering.'
+    - 'Prefer cursor pagination over deep skip/take for large tables.'
+    - 'Use an external pooler (e.g., PgBouncer) or explicit adapter connection limits in serverless/container workloads.'
+  decision_table:
+    - when: 'A query needs PostgreSQL features Prisma API cannot express well'
+      then: 'Use $queryRaw with tagged templates and typed result mapping'
+      avoid: 'Unsafe string-built SQL'
+    - when: 'A transaction has dependent steps'
+      then: 'Use interactive $transaction(async (tx) => ...) with explicit timeout/maxWait'
+      avoid: 'Batch $transaction([...]) for interdependent operations'

package/data/rules/python.yaml

@@ -0,0 +1,31 @@
+id: python
+category: language
+tags:
+  - python
+priority: 55
+content:
+  constraints:
+    - 'DO NOT use Any in type hints. Use object or concrete generics instead.'
+    - 'DO NOT use mutable default arguments. Use None + factory inside the function.'
+    - 'DO NOT use bare except or broad except Exception. Catch specific exception types.'
+    - 'DO NOT use wildcard imports.'
+    - 'DO NOT use type(x) == T checks. Prefer isinstance() or protocol-based checks.'
+    - 'DO NOT use # type: ignore without an explicit error code.'
+  guidelines:
+    - 'Annotate all function parameters and return types, including -> None.'
+    - 'Use Pydantic v2 BaseModel for DTO/config schemas; use field_validator/model_validator APIs.'
+    - 'Use TypeAlias, TypeVar, ParamSpec, TypedDict, and Literal to model intent clearly.'
+    - 'Keep business logic in pure *_logic.py modules; keep routers/services thin.'
+    - 'Use @dataclass(frozen=True) for immutable value objects that do not need runtime validation.'
+    - 'Use pathlib.Path for filesystem paths.'
+    - 'Use f-strings for string formatting.'
+  decision_table:
+    - when: 'Structured input/output needs validation or serialization'
+      then: 'Use Pydantic v2 models'
+      avoid: 'Unvalidated dict payloads'
+    - when: 'Immutable value object without runtime validation is enough'
+      then: 'Use @dataclass(frozen=True)'
+      avoid: 'Using Pydantic where validation is unnecessary'
+    - when: 'Runtime type narrowing is needed'
+      then: 'Use isinstance() or model_validate()'
+      avoid: 'Fragile type()/hasattr() checks'

package/data/rules/react-typescript.yaml

@@ -0,0 +1,11 @@
+id: react-typescript
+category: framework
+tags:
+  - typescript
+  - react
+priority: 60
+content:
+  constraints:
+    - 'DO NOT use React.FC or FC. Type props directly and destructure them.'
+  guidelines:
+    - 'Use readonly for array and object props.'

package/data/rules/role-persona.yaml

@@ -0,0 +1,14 @@
+id: role-persona
+category: persona
+tags:
+  - general
+  - persona
+priority: 90
+content:
+  constraints:
+    - "DO NOT write patronizing tutorials (e.g., 'First, let me explain what React is...')."
+  guidelines:
+    - 'You are an expert Senior Full-Stack Developer.'
+    - 'Assume the user is a senior developer, but may be unfamiliar with specific domains or patterns.'
+    - 'When choosing a pattern, library, or architectural approach, briefly explain WHY it was chosen over alternatives.'
+    - 'Focus on high-level architecture, edge cases, performance optimization, and maintainability.'

package/data/rules/shadcn-ui.yaml

@@ -0,0 +1,36 @@
+id: shadcn-ui
+category: ui
+tags:
+  - typescript
+  - react
+  - shadcn-ui
+  - tailwind
+priority: 35
+content:
+  constraints:
+    - 'DO NOT reimplement components already available in shadcn/ui. Add and compose existing primitives first.'
+    - 'DO NOT edit generated shadcn source files directly (components/ui/*). Extend via wrappers or className overrides.'
+    - 'DO NOT overuse arbitrary Tailwind values for stable design tokens.'
+    - 'DO NOT use inline style props for static values. Use Tailwind classes.'
+  guidelines:
+    - 'Check shadcn component catalog before building custom UI primitives.'
+    - 'Use cn() for conditional class composition and tailwind-merge conflict resolution.'
+    - 'Use shadcn composition patterns (Trigger/Content/Header/etc.) for complex components.'
+    - 'Use cva for variant-heavy components.'
+    - 'Keep theme tokens CSS-variable based and map them in Tailwind config.'
+    - 'Use mobile-first responsive classes (sm/md/lg progression).'
+    - 'Preserve accessibility (aria-label or sr-only text for icon-only controls).'
+    - 'Use named lucide-react icon imports only.'
+  decision_table:
+    - when: 'A needed UI element exists in shadcn or can be composed from Radix primitives'
+      then: 'Use shadcn composition'
+      avoid: 'Custom rebuild from scratch'
+    - when: 'No suitable primitive exists and interaction is domain-specific'
+      then: 'Build a custom component'
+      avoid: 'Forcing unrelated shadcn primitives'
+    - when: 'A component has variants'
+      then: 'Model variants with cva'
+      avoid: 'Large conditional className branches in JSX'
+    - when: 'Styling approach is needed'
+      then: 'Use Tailwind utilities by default'
+      avoid: 'Switching to CSS Modules for normal component styling'

package/data/rules/sqlalchemy.yaml

@@ -0,0 +1,32 @@
+id: sqlalchemy
+category: database
+tags:
+  - python
+  - sqlalchemy
+  - postgresql
+priority: 38
+content:
+  constraints:
+    - 'DO NOT use legacy session.query() patterns. Use SQLAlchemy 2.x select()/insert()/update().'
+    - 'DO NOT execute raw SQL strings directly outside migrations. Use ORM or text() with bound params.'
+    - 'DO NOT call session.commit() from scattered layers. Commit once at service/unit-of-work boundary.'
+    - 'DO NOT omit created_at/updated_at on mutable models.'
+    - 'DO NOT change schema without Alembic migrations.'
+  guidelines:
+    - 'Use Mapped[T] + mapped_column() declarative mappings.'
+    - 'Define relationships explicitly with back_populates.'
+    - 'Use AsyncSession + async_sessionmaker for async FastAPI stacks.'
+    - 'Implement soft delete with deleted_at and default filtered queries.'
+    - 'Use StrEnum-backed string enums for migration-safe enum storage.'
+    - 'Declare indexes/unique constraints explicitly in __table_args__. '
+    - 'Prevent N+1: use selectinload() for 1:N (separate IN query) and joinedload() for N:1/1:1 (JOIN). Never rely on lazy loading by default.'
+  decision_table:
+    - when: 'Routine CRUD is needed'
+      then: 'Use ORM expressions (select/insert/update)'
+      avoid: 'Hand-written raw SQL by default'
+    - when: 'Complex analytical SQL is needed'
+      then: 'Use text() with bound params or a fit-for-purpose analytical engine'
+      avoid: 'Unreadable ORM expression chains'
+    - when: 'Schema changes are required'
+      then: 'Generate Alembic migration and review before apply'
+      avoid: 'Manual untracked DDL changes'

package/data/rules/typescript.yaml

@@ -0,0 +1,22 @@
+id: typescript
+category: language
+tags:
+  - typescript
+priority: 65
+content:
+  constraints:
+    - 'DO NOT use interface. Use type aliases consistently.'
+    - 'DO NOT use enum. Use const objects with inferred literal unions.'
+    - 'DO NOT use any. Use unknown and narrow with runtime/type guards.'
+    - 'DO NOT use non-null assertion (!). Handle null/undefined explicitly with ?. and ??.'
+    - 'DO NOT use .then() chains for normal async flows. Use async/await.'
+    - 'DO NOT throw raw strings. Throw Error objects and narrow caught errors from unknown.'
+  guidelines:
+    - 'Use arrow functions only. Annotate return types for exported functions.'
+    - 'Use import type for type-only imports. Use absolute paths (@/...) only.'
+    - 'Use as const for static config objects.'
+    - 'Keep business logic in *.logic.ts and stateless helpers in *.util.ts.'
+  decision_table:
+    - when: 'You feel forced to use an as assertion'
+      then: 'Prefer schema parse (e.g., Zod) or explicit type guards first'
+      avoid: 'Bypassing the type system with unchecked assertions'