nitm-ai-dev-toolkit 3.0.15

package/src/repo/.opencode/commands/tasks.md

@@ -0,0 +1,16 @@
+---
+description: "Generate an actionable task list from a specification or plan"
+---
+
+# Generate Task List
+
+## Agent Dispatch
+
+> **Recommended agent:** `planner`
+> Task breakdown and management
+
+## Arguments
+
+$ARGUMENTS
+
+@.claude/prompt-snippets/tasks.md

package/src/repo/.opencode/opencode.json

@@ -0,0 +1,9 @@
+{
+	"$schema": "https://opencode.ai/config.json",
+	"instructions": ["AGENTS.md", ".opencode/rules/*.md", ".agents/skills/orient-to-recent-work/SKILL.md"],
+	"skills": {
+		"paths": [".agents/skills/**/*.md", ".claude/skills/**/*.md"]
+	},
+	"plugin": [".opencode/plugins/ponytail.mjs"],
+	"lsp": true
+}

package/src/repo/.opencode/plugins/ponytail.mjs

@@ -0,0 +1,79 @@
+// ponytail — OpenCode plugin.
+//
+// Injects the ponytail ruleset into every chat's system prompt at the active
+// intensity, and persists /ponytail mode switches. Reuses the shared instruction
+// builder so Claude Code, Codex, pi, and OpenCode all read one source of truth.
+//
+// OpenCode loads this as a server plugin — add it to your opencode.json:
+//   { "plugin": ["./.opencode/plugins/ponytail.mjs"] }
+
+import { createRequire } from 'module';
+import fs from 'fs';
+import os from 'os';
+import path from 'path';
+import { fileURLToPath } from 'url';
+
+const __dirname = path.dirname(fileURLToPath(import.meta.url));
+
+// The shared instruction builder is CommonJS; bridge to it from this ES module.
+const require = createRequire(import.meta.url);
+const { getPonytailInstructions } = require('../../hooks/ponytail-instructions');
+const { getDefaultMode, normalizePersistedMode } = require('../../hooks/ponytail-config');
+
+// OpenCode has no flag-file convention of its own; keep mode beside its config.
+const statePath = path.join(
+  process.env.XDG_CONFIG_HOME || path.join(os.homedir(), '.config'),
+  'opencode',
+  '.ponytail-active',
+);
+
+function readMode() {
+  try {
+    return normalizePersistedMode(fs.readFileSync(statePath, 'utf8').trim()) || getDefaultMode();
+  } catch (e) {
+    return getDefaultMode();
+  }
+}
+
+function writeMode(mode) {
+  fs.mkdirSync(path.dirname(statePath), { recursive: true });
+  fs.writeFileSync(statePath, mode);
+}
+
+export default async ({ client } = {}) => {
+  const log = (level, message) => {
+    try { client && client.app && client.app.log({ body: { service: 'ponytail', level, message } }); } catch (e) {}
+  };
+
+  const ponytailSkillsDir = path.resolve(__dirname, '../../.agents/skills');
+
+  return {
+    // Register skills directory so opencode discovers ponytail skills.
+    config: async (config) => {
+      config.skills = config.skills || {};
+      config.skills.paths = config.skills.paths || [];
+      if (!config.skills.paths.includes(ponytailSkillsDir)) {
+        config.skills.paths.push(ponytailSkillsDir);
+      }
+    },
+
+    // Append the ruleset to the system prompt every turn.
+    'experimental.chat.system.transform': async (_input, output) => {
+      const mode = readMode();
+      if (mode === 'off') return;
+      output.system.push(getPonytailInstructions(mode));
+    },
+
+    // Persist `/ponytail <level>` so the next turn's injection follows it.
+    // ponytail: mode applies from the next message, not the current one — the
+    // transform reads the flag the command writes. Good enough; switch to a
+    // synchronous store if same-turn switching ever matters.
+    'command.execute.before': async (input) => {
+      if (!input || input.command !== 'ponytail') return;
+      // `off` is persisted like any mode; the transform reads it and stays silent.
+      const mode = normalizePersistedMode((input.arguments || '').trim()) || getDefaultMode();
+      writeMode(mode);
+      log('info', 'ponytail ' + mode);
+    },
+  };
+};

package/src/repo/.opencode/rules/agent-conduct.md

@@ -0,0 +1,11 @@
+# Agent Conduct
+
+Agent conduct and clarification rules for ambiguous requirements.
+
+@.claude/rules-snippets/agent-conduct.md
+
+## Key points
+
+- Use coordinator agents for non-trivial multi-step tasks (orchestration checkpoint).
+- Ask for clarification on ambiguous requirements before making assumptions.
+- Never silently change database schemas, API contracts, or authentication flows.

package/src/repo/.opencode/rules/api-server.md

@@ -0,0 +1,11 @@
+# API & Server
+
+API and server-side development standards.
+
+@.claude/rules-snippets/api-server.md
+
+## Key points
+
+- Follow {{API_ROUTE_PATTERN}} for API route conventions.
+- Validate all input data before processing.
+- Return consistent response formats with proper HTTP status codes.

package/src/repo/.opencode/rules/coding-standards.md

@@ -0,0 +1,11 @@
+# Coding Standards
+
+Coding standards and language conventions.
+
+@.claude/rules-snippets/coding-standards.md
+
+## Key points
+
+- All code must follow {{LANGUAGE}} type safety rules and {{FRAMEWORK}} conventions.
+- Keep functions focused and manageable (under 50-75 lines).
+- Use try-catch for async operations; leverage {{FRAMEWORK}} error utilities.

package/src/repo/.opencode/rules/component-structure.md

@@ -0,0 +1,11 @@
+# Component Structure
+
+Component structure and composition patterns.
+
+@.claude/rules-snippets/component-structure.md
+
+## Key points
+
+- Follow the {{COMPONENT_PATTERN}} pattern for all components.
+- Use clear and descriptive naming for props, events, and methods.
+- Use bracketed identifiers for logs: `[ComponentName]: message`.

package/src/repo/.opencode/rules/core-libraries.md

@@ -0,0 +1,11 @@
+# Core Libraries
+
+Core library and framework usage conventions.
+
+@.claude/rules-snippets/core-libraries.md
+
+## Key points
+
+- Use {{UTILITY_LIBRARY}} for common utilities and {{STATE_MANAGEMENT}} for state.
+- Use {{STYLING}} for styling; prefer utility classes over custom CSS.
+- Use {{UI_LIBRARY}} for UI components; check existing components before creating new ones.

package/src/repo/.opencode/rules/environment-tooling.md

@@ -0,0 +1,11 @@
+# Environment & Tooling
+
+Environment and tooling configuration.
+
+@.claude/rules-snippets/environment-tooling.md
+
+## Key points
+
+- Tailor commands to the user's OS and shell.
+- Use `{{PACKAGE_MANAGER}}` for package management.
+- Follow project-specific tooling rules for linting and formatting.

package/src/repo/.opencode/rules/logging-comments.md

@@ -0,0 +1,11 @@
+# Logging & Comments
+
+Logging identifiers and code comment conventions.
+
+@.claude/rules-snippets/logging-comments.md
+
+## Key points
+
+- Comment complex logic and non-obvious implementations.
+- Use bracketed identifiers for logs: `[ModuleName]: message`.
+- Remove debug logs before committing to main branch.

package/src/repo/.opencode/rules/logging.md

@@ -0,0 +1,11 @@
+# Logging Standards
+
+Structured logging standards and best practices.
+
+@.claude/rules-snippets/logging.md
+
+## Key points
+
+- Use bracketed tags: `[Source] [Context]: Message | Details`.
+- Use appropriate log levels: error, warn, info, debug.
+- Never log passwords, API keys, tokens, or PII — sanitize before logging.

package/src/repo/.opencode/rules/ponytail.md

@@ -0,0 +1,3 @@
+# Ponytail, lazy senior dev mode
+
+Full content: [.claude/rules-snippets/ponytail.md](../../.claude/rules-snippets/ponytail.md)

package/src/repo/.opencode/rules/prisma-migrations.md

@@ -0,0 +1,11 @@
+# Prisma Migrations
+
+Database migration and schema management.
+
+@.claude/rules-snippets/prisma-migrations.md
+
+## Key points
+
+- Follow {{DATABASE_SYNC_RULE}} for database synchronization.
+- Create migrations with descriptive names; apply to dev database before committing.
+- Run tests after schema modifications.

package/src/repo/.opencode/rules/project-context.md

@@ -0,0 +1,11 @@
+# Project Context
+
+Project context and documentation references.
+
+@.claude/rules-snippets/project-context.md
+
+## Key points
+
+- Review project documentation before generating code or suggestions.
+- Reference AGENTS.md for project overview, agent conduct rules, and skills.
+- Reference `.claude/rules-snippets/` for detailed standards (coding, testing, deployment, logging, etc.).

package/src/repo/.opencode/rules/server-client-separation.md

@@ -0,0 +1,11 @@
+# Server-Client Separation
+
+Server and client code boundary enforcement.
+
+@.claude/rules-snippets/server-client-separation.md
+
+## Key points
+
+- Never import server-only code in client components.
+- Use API endpoints to expose server functionality to clients.
+- Mark server-only modules clearly (e.g., `.server.{{LANGUAGE_EXTENSION}}`).

package/src/repo/.opencode/rules/subagent-workflow.md

@@ -0,0 +1,11 @@
+# Subagent Workflow
+
+Subagent workflow and orchestration patterns.
+
+@.claude/rules-snippets/subagent-workflow.md
+
+## Key points
+
+- Default to orchestrator + subagents for non-trivial work (features, refactors, multi-file fixes).
+- Use a coordinator agent (Feature Builder or TDD) as the entry point.
+- Match task domain to the right specialist before defaulting to Implementer.

package/src/repo/.opencode/rules/testing-quality.md

@@ -0,0 +1,11 @@
+# Testing & Quality
+
+Testing standards and quality gates.
+
+@.claude/rules-snippets/testing-quality.md
+
+## Key points
+
+- Ensure lint, test, and build pass before committing.
+- Use {{TEST_FRAMEWORK}} for unit/component tests and {{E2E_FRAMEWORK}} for E2E tests.
+- Aim for meaningful test coverage of business logic.

package/src/repo/.opencode/rules/ui-accessibility.md

@@ -0,0 +1,11 @@
+# UI & Accessibility
+
+UI accessibility and responsive design standards.
+
+@.claude/rules-snippets/ui-accessibility.md
+
+## Key points
+
+- Develop with a mobile-first approach.
+- Adhere to WCAG 2.1 AA accessibility standards.
+- Use semantic HTML elements and ensure keyboard navigation.

package/src/repo/.opencode/rules/version-control.md

@@ -0,0 +1,11 @@
+# Version Control
+
+Version control and commit conventions.
+
+@.claude/rules-snippets/version-control.md
+
+## Key points
+
+- Use conventional commit format: `<type>(<scope>): <description>`.
+- Types: feat, fix, docs, refactor, test, chore, style, perf.
+- Include ticket reference when applicable.

package/src/repo/.opencode/rules/what-to-avoid.md

@@ -0,0 +1,11 @@
+# What to Avoid
+
+Patterns and practices to avoid.
+
+@.claude/rules-snippets/what-to-avoid.md
+
+## Key points
+
+- No deprecated {{FRAMEWORK}} features or global CSS outside {{STYLING}} configuration.
+- No direct DOM manipulation; use framework reactivity.
+- No custom solutions for problems solved by core libraries.

package/src/repo/.vscode/mcp.json

@@ -0,0 +1,13 @@
+{
+    "servers": {
+        // Add your MCP servers here
+        // Example:
+        // "example-server": {
+        //     "command": "npx",
+        //     "args": ["-y", "@example/mcp-server@latest"],
+        //     "env": {
+        //         "API_KEY": "${API_KEY}"
+        //     }
+        // }
+    }
+}