create-agentic-lemon 0.1.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Ethereal Lemons
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,61 @@
+# create-agentic-lemon
+
+An agent-agnostic workspace generator that creates a reusable AI operating system folder structure.
+
+Treat your AI assistant context as files and folders instead of transient, ephemeral chat history. This workspace structure helps any file-reading AI coding tool (ChatGPT, Claude, Cursor, Windsurf, Copilot, etc.) understand your project context, guidelines, workflows, decisions, and learnings instantly.
+
+## Usage
+
+You can generate a workspace with a single command without installing the package:
+
+```bash
+npm create agentic-lemon@latest my-workspace
+```
+
+Or using `npx`:
+
+```bash
+npx create-agentic-lemon@latest my-workspace
+```
+
+Or install it globally and use either command alias:
+
+```bash
+npm i -g create-agentic-lemon
+agentic-lemon my-workspace
+create-agentic-lemon my-workspace
+```
+
+### Options
+
+*   `--force`: Overwrite existing template files in the workspace (leaves other files intact).
+
+---
+
+## Workspace Structure
+
+The generated workspace structure includes:
+
+*   **`AGENTS.md`**: Global operating rules for the AI.
+*   **`PROJECT_CONTEXT.md`**: High-level metadata about project scope, users, systems, constraints, and styling preferences.
+*   **`context/`**: Stable knowledge files (e.g. database schema, systems documentation, coding styles).
+*   **`skills/`**: Repeatable workflows documented as reusable playbooks (e.g. software development, debugging, reports).
+*   **`memory/`**: High-level cross-skill memory files including decisions, preferences, and recurring corrections.
+*   **`outputs/`**: Dedicated subdirectories for drafts, approved content, snippets, and debug notes.
+*   **`references/`**: Links to external documentation and sources.
+
+---
+
+## How to use with an AI Assistant
+
+Open the generated workspace in your editor. In your AI chat window, prompt the AI:
+
+> "Read AGENTS.md first, then PROJECT_CONTEXT.md, then any relevant files under context/ and skills/ before answering."
+
+When the AI makes a mistake or you correct something reusable, save that learning in the respective skill's `learnings.md` or global `memory/recurring-corrections.md` so the AI remembers it next time!
+
+---
+
+## License
+
+MIT

package/bin/agentic-lemon.js

@@ -0,0 +1,167 @@
+#!/usr/bin/env node
+
+import fs from 'fs';
+import path from 'path';
+import { fileURLToPath } from 'url';
+
+const __filename = fileURLToPath(import.meta.url);
+const __dirname = path.dirname(__filename);
+
+// Helper to print usage/help
+function printUsage() {
+  console.log(`
+Usage:
+  npm create agentic-lemon@latest <workspace-name> [options]
+  npx create-agentic-lemon@latest <workspace-name> [options]
+  agentic-lemon <workspace-name> [options]
+  create-agentic-lemon <workspace-name> [options]
+
+Options:
+  --force       Overwrite existing files in the workspace (doesn't delete other files)
+  -h, --help    Show this help message
+`);
+}
+
+function logError(msg) {
+  console.error(`\x1b[31mError:\x1b[0m ${msg}`);
+}
+
+function logSuccess(msg) {
+  console.log(`\x1b[32mSuccess:\x1b[0m ${msg}`);
+}
+
+function logInfo(msg) {
+  console.log(msg);
+}
+
+function validateTargetPath(targetPath) {
+  if (fs.existsSync(targetPath)) {
+    if (!fs.statSync(targetPath).isDirectory()) {
+      throw new Error(`Target path exists and is not a directory: ${targetPath}`);
+    }
+
+    return;
+  }
+
+  let currentPath = path.dirname(targetPath);
+
+  while (currentPath !== path.dirname(currentPath)) {
+    if (fs.existsSync(currentPath)) {
+      if (!fs.statSync(currentPath).isDirectory()) {
+        throw new Error(`Cannot create workspace because parent path is not a directory: ${currentPath}`);
+      }
+
+      return;
+    }
+
+    currentPath = path.dirname(currentPath);
+  }
+}
+
+async function main() {
+  const args = process.argv.slice(2);
+
+  // Parse arguments
+  let targetDirName = null;
+  let force = false;
+  let showHelp = false;
+
+  for (const arg of args) {
+    if (arg === '--force') {
+      force = true;
+    } else if (arg === '--help' || arg === '-h') {
+      showHelp = true;
+    } else if (arg.startsWith('-')) {
+      logError(`Unknown option ${arg}`);
+      printUsage();
+      process.exit(1);
+    } else {
+      if (targetDirName === null) {
+        targetDirName = arg;
+      } else {
+        logError(`Unexpected argument: ${arg}`);
+        printUsage();
+        process.exit(1);
+      }
+    }
+  }
+
+  if (showHelp) {
+    printUsage();
+    process.exit(0);
+  }
+
+  // If targetDirName is omitted, default to 'agentic-os'
+  if (!targetDirName) {
+    targetDirName = 'agentic-os';
+  }
+
+  const targetPath = path.resolve(process.cwd(), targetDirName);
+  const templatesPath = path.resolve(__dirname, '../templates');
+
+  if (!fs.existsSync(templatesPath)) {
+    logError(`Templates directory not found at ${templatesPath}. Please ensure the package is installed correctly.`);
+    process.exit(1);
+  }
+
+  try {
+    validateTargetPath(targetPath);
+  } catch (err) {
+    logError(err.message);
+    process.exit(1);
+  }
+
+  logInfo(`Initializing Agentic OS workspace at \x1b[36m${targetPath}\x1b[0m...`);
+  if (force) {
+    logInfo('Running in force mode: existing template files will be overwritten.');
+  }
+
+  try {
+    // Recursive directory walker and copier
+    function copyRecursive(src, dest) {
+      const stats = fs.statSync(src);
+      if (stats.isDirectory()) {
+        if (!fs.existsSync(dest)) {
+          fs.mkdirSync(dest, { recursive: true });
+        }
+        const entries = fs.readdirSync(src);
+        for (const entry of entries) {
+          copyRecursive(path.join(src, entry), path.join(dest, entry));
+        }
+      } else {
+        const destDir = path.dirname(dest);
+        if (!fs.existsSync(destDir)) {
+          fs.mkdirSync(destDir, { recursive: true });
+        }
+
+        if (fs.existsSync(dest)) {
+          if (force) {
+            fs.copyFileSync(src, dest);
+            console.log(`  \x1b[33m[Overwritten]\x1b[0m ${path.relative(targetPath, dest)}`);
+          } else {
+            console.log(`  \x1b[90m[Skipped]\x1b[0m     ${path.relative(targetPath, dest)} (already exists)`);
+          }
+        } else {
+          fs.copyFileSync(src, dest);
+          console.log(`  \x1b[32m[Created]\x1b[0m     ${path.relative(targetPath, dest)}`);
+        }
+      }
+    }
+
+    copyRecursive(templatesPath, targetPath);
+
+    logSuccess(`\nSuccessfully generated Agentic OS workspace!`);
+    logInfo(`
+Next steps:
+  1. cd ${targetDirName}
+  2. Open AGENTS.md and PROJECT_CONTEXT.md to customize your workspace
+  3. Reference AGENTS.md in your AI assistant chats to start using the OS
+`);
+    process.exit(0);
+  } catch (err) {
+    logError(`Failed to generate workspace: ${err.message}`);
+    process.exit(1);
+  }
+}
+
+main();

package/package.json

@@ -0,0 +1,41 @@
+{
+  "name": "create-agentic-lemon",
+  "version": "0.1.0",
+  "description": "Create an agent-agnostic AI operating system folder structure.",
+  "type": "module",
+  "bin": {
+    "agentic-lemon": "bin/agentic-lemon.js",
+    "create-agentic-lemon": "bin/agentic-lemon.js"
+  },
+  "scripts": {
+    "test": "node scripts/test.js",
+    "release:check": "node scripts/release-check.js",
+    "prepublishOnly": "node scripts/release-check.js --publish"
+  },
+  "files": [
+    "bin",
+    "templates"
+  ],
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/Ethereal-Lemons/agentic-lemon.git"
+  },
+  "bugs": {
+    "url": "https://github.com/Ethereal-Lemons/agentic-lemon/issues"
+  },
+  "homepage": "https://github.com/Ethereal-Lemons/agentic-lemon#readme",
+  "packageManager": "npm@11.13.0",
+  "engines": {
+    "node": ">=18.0.0"
+  },
+  "keywords": [
+    "ai",
+    "agents",
+    "agentic-os",
+    "agentic-lemon",
+    "ai-workspace",
+    "context-engineering",
+    "prompt-engineering"
+  ],
+  "license": "MIT"
+}

package/templates/AGENTS.md

@@ -0,0 +1,40 @@
+# AI Operating Rules
+
+This workspace is agent-agnostic. Any AI assistant can use it by reading these files before performing work.
+
+## How to Use This Workspace
+
+1. Read this file first.
+2. Read `PROJECT_CONTEXT.md`.
+3. Read relevant files inside `context/`.
+4. Choose the most relevant skill inside `skills/`.
+5. Check that skill's `learnings.md` before answering.
+6. Produce the requested output.
+7. When the user corrects something reusable, suggest adding it to the relevant `learnings.md` file.
+
+## Global Rules
+
+- Be direct and practical.
+- Prefer complete, usable outputs over partial suggestions.
+- Preserve existing project structure unless the user asks for refactoring.
+- Do not remove existing filters, rules, or validations unless explicitly requested.
+- State assumptions when information is missing.
+- Do not expose secrets, credentials, tokens, private keys, or sensitive data.
+- Use project terminology from `context/glossary.md` when available.
+- Check `memory/recurring-corrections.md` before finalizing technical work.
+
+## Output Rules
+
+- For code, provide complete files or clear replacement blocks.
+- For SQL, provide runnable queries or procedures.
+- For documentation, use clean Markdown.
+- For debugging, explain the root cause and the fix.
+- For reports, clarify date ranges, sorting, and filters.
+
+## Learning Rules
+
+When a correction is likely to matter again:
+
+- Add it to the related skill's `learnings.md`.
+- If it applies globally, add it to `memory/recurring-corrections.md`.
+- If it records a major direction, add it to `memory/decisions.md`.

package/templates/PROJECT_CONTEXT.md

@@ -0,0 +1,29 @@
+# Project Context
+
+## Project Name
+
+<!-- Add project name here -->
+
+## Purpose
+
+<!-- Explain what this workspace is for -->
+
+## Main Users
+
+<!-- Who uses this project/system/workflow? -->
+
+## Main Systems
+
+<!-- List important systems, apps, databases, websites, services, or workflows -->
+
+## Important Constraints
+
+<!-- Add constraints the AI must respect -->
+
+## Preferred Style
+
+<!-- Explain preferred tone, detail level, formatting, and output style -->
+
+## Things the AI Should Avoid
+
+<!-- Add common mistakes or things not to do -->

package/templates/README.md

@@ -0,0 +1,23 @@
+# AI Agentic OS Workspace
+
+Welcome to your Agentic OS workspace! This folder structure is designed to organize context, workflows, rules, and memory for any AI assistant (ChatGPT, Claude, Cursor, Windsurf, Copilot, etc.) that you pair program or collaborate with.
+
+## Directory Structure Overview
+
+- **`AGENTS.md`**: Global operating rules for the AI.
+- **`PROJECT_CONTEXT.md`**: High-level details about the project, target audience, systems, and guidelines.
+- **`context/`**: Slow-changing, stable knowledge about database schemas, system architecture, API guidelines, glossary, etc.
+- **`skills/`**: Repeatable workflows (software development, database queries, report generation, debugging, etc.). Each skill contains its process guidelines, examples, templates, checklists, and persistent learnings.
+- **`memory/`**: High-level cross-skill memory including architecture decisions, preferences, and recurring corrections.
+- **`outputs/`**: Workspace for AI-generated drafts, approved deliverables, code snippets, and debugging notes.
+- **`references/`**: Links to external documentation, source references, and APIs.
+
+## How to use with an AI Assistant
+
+Start your conversation or chat session by prompting the AI:
+
+```txt
+Read AGENTS.md first, then PROJECT_CONTEXT.md, then any relevant files under context/ and skills/ before answering.
+```
+
+When you correct an AI's behavior or logic, save that learning in the respective skill's `learnings.md` or the global `memory/recurring-corrections.md` file so the AI remembers it next time!

package/templates/context/architecture.md

@@ -0,0 +1,19 @@
+# Architecture
+
+## Overview
+
+<!-- Describe the architecture at a high level -->
+
+## Components
+
+| Component | Purpose | Notes |
+|---|---|---|
+|  |  |  |
+
+## Data Flow
+
+<!-- Describe how data moves through the system -->
+
+## Integrations
+
+<!-- List external services, APIs, databases, or tools -->

package/templates/context/coding-style.md

@@ -0,0 +1,18 @@
+# Coding Style
+
+## General
+
+- Keep code readable.
+- Prefer explicit names.
+- Avoid unnecessary abstractions.
+- Preserve existing behavior unless asked to change it.
+
+## Error Handling
+
+- Handle missing or null values safely.
+- Avoid undefined indexes or unsafe assumptions.
+
+## Formatting
+
+- Keep indentation consistent with the existing file.
+- Return complete replacement code when requested.

package/templates/context/constraints.md

@@ -0,0 +1,19 @@
+# Constraints
+
+## Technical Constraints
+
+- 
+
+## Business Constraints
+
+- 
+
+## Security Constraints
+
+- Do not expose credentials.
+- Do not log secrets.
+- Do not commit private keys or tokens.
+
+## Output Constraints
+
+- 

package/templates/context/database-schema.md

@@ -0,0 +1,28 @@
+# Database Schema
+
+## Databases
+
+| Database | Purpose | Notes |
+|---|---|---|
+|  |  |  |
+
+## Tables
+
+### Example Table
+
+```sql
+example_table
+- id
+- name
+- created_at
+```
+
+## Relationships
+
+- 
+
+## Query Rules
+
+- Be careful with date sorting.
+- Preserve existing filters unless explicitly asked to remove them.
+- Prefer clear aliases.

package/templates/context/glossary.md

@@ -0,0 +1,5 @@
+# Glossary
+
+| Term | Meaning | Notes |
+|---|---|---|
+|  |  |  |

package/templates/context/project-overview.md

@@ -0,0 +1,21 @@
+# Project Overview
+
+## Summary
+
+This folder contains reusable context for AI-assisted work.
+
+## Goals
+
+- Reduce repeated explanations.
+- Keep AI output consistent.
+- Document repeatable workflows.
+- Preserve useful corrections.
+- Store approved outputs.
+
+## Current Priorities
+
+- 
+
+## Known Risks
+
+- 

package/templates/context/systems.md

@@ -0,0 +1,17 @@
+# Systems
+
+Document important systems here.
+
+## System Template
+
+### System Name
+
+Purpose:
+
+Main files:
+
+Main database tables:
+
+Known issues:
+
+Important rules:

package/templates/memory/changelog.md

@@ -0,0 +1,5 @@
+# Changelog
+
+## YYYY-MM-DD
+
+- 

package/templates/memory/decisions.md

@@ -0,0 +1,13 @@
+# Decisions
+
+Track important decisions here.
+
+## Format
+
+### YYYY-MM-DD — Decision Title
+
+Decision:
+
+Reason:
+
+Impact:

package/templates/memory/preferences.md

@@ -0,0 +1,19 @@
+# Preferences
+
+Track user or team preferences here.
+
+## Communication
+
+- 
+
+## Code
+
+- 
+
+## Documentation
+
+- 
+
+## Reports
+
+- 

package/templates/memory/recurring-corrections.md

@@ -0,0 +1,7 @@
+# Recurring Corrections
+
+Track corrections that apply across the whole workspace.
+
+## Corrections
+
+- 

package/templates/outputs/approved/.gitkeep

@@ -0,0 +1 @@
+# Keep directory in git

package/templates/outputs/debug-notes/.gitkeep

@@ -0,0 +1 @@
+# Keep directory in git

package/templates/outputs/drafts/.gitkeep

@@ -0,0 +1 @@
+# Keep directory in git

package/templates/outputs/snippets/.gitkeep

@@ -0,0 +1 @@
+# Keep directory in git

package/templates/references/external-docs.md

@@ -0,0 +1,5 @@
+# External Documentation
+
+Summaries or references to external library/framework documentation.
+
+- 

package/templates/references/links.md

@@ -0,0 +1,5 @@
+# Links
+
+A directory of useful URLs and portals for the project.
+
+- [Main Repository](https://github.com/Ethereal-Lemons)

package/templates/references/sources.md

@@ -0,0 +1,5 @@
+# Sources
+
+Documentation, technical specifications, and reference materials.
+
+- 

package/templates/skills/database-work/common-errors.md

@@ -0,0 +1,8 @@
+# Common Database Errors
+
+Keep track of query errors and performance pitfalls.
+
+## Pitfall: Implicit Type Conversion
+- **Symptom:** Index is ignored, leading to slow queries.
+- **Cause:** Comparing numeric field to string value or vice-versa.
+- **Fix:** Ensure matching data types.

package/templates/skills/database-work/examples.md

@@ -0,0 +1,12 @@
+# Database Work Examples
+
+Approved examples of high-performing and correct queries.
+
+## Example: Inclusive Date Filtering
+
+```sql
+SELECT id, email, created_at
+FROM users
+WHERE created_at >= '2026-01-01 00:00:00'
+  AND created_at < '2026-02-01 00:00:00'; -- Note: Exclusive upper bound to capture entire last day safely
+```

package/templates/skills/database-work/learnings.md

@@ -0,0 +1,5 @@
+# Database Work Learnings
+
+Record resolved DB issues and learnings.
+
+- 

package/templates/skills/database-work/query-patterns.md

@@ -0,0 +1,12 @@
+# Database Query Patterns
+
+Common query templates for analytics, reporting, and management.
+
+## Pattern: Pagination
+
+```sql
+SELECT id, name
+FROM products
+ORDER BY name ASC
+LIMIT :limit OFFSET :offset;
+```

package/templates/skills/database-work/skill.md

@@ -0,0 +1,21 @@
+# Skill: Database Work
+
+Use this skill when creating, fixing, or reviewing SQL queries, stored procedures, reports, migrations, or database-related logic.
+
+## Process
+
+1. Identify the database engine.
+2. Identify the target tables and columns.
+3. Preserve filters unless the user asks to remove them.
+4. Check joins carefully.
+5. Check date handling carefully.
+6. Avoid sorting formatted date strings.
+7. Return complete runnable SQL when requested.
+
+## Common Mistakes
+
+- Ordering formatted dates as strings.
+- Missing join conditions.
+- Filtering after a left join in a way that turns it into an inner join.
+- Forgetting null handling.
+- Removing business filters accidentally.

package/templates/skills/debugging/checklist.md

@@ -0,0 +1,10 @@
+# Debugging Checklist
+
+Follow these steps when diagnosing an issue:
+
+- [ ] Replicate the bug: Can you trigger it reliably?
+- [ ] Read the logs: Check stack traces, console messages, network calls, and database logs.
+- [ ] Isolate the cause: Is the issue frontend, backend, database, network, or environment?
+- [ ] Confirm inputs: Are variables or params formatted correctly?
+- [ ] Formulate fix: Implement a minimal, safe, targeted fix.
+- [ ] Double-check: Make sure the fix doesn't break related modules.

package/templates/skills/debugging/common-errors.md

@@ -0,0 +1,7 @@
+# Common Errors
+
+A list of frequently occurring errors and their general resolution guides.
+
+## Error: Permission Denied on File Write
+- **Cause:** Process does not have write permissions for the target directory.
+- **Fix:** Verify user permissions, check ownership of folder, or run with appropriate elevated context.

package/templates/skills/debugging/examples.md

@@ -0,0 +1,15 @@
+# Debugging Examples
+
+Store examples of successfully debugged issues, detailing the symptoms, root cause, and fix.
+
+## Example: Null Pointer Exception on User profile
+
+### Symptoms
+- 500 error when clicking Profile page.
+- Console error: `Cannot read properties of undefined (reading 'name')`.
+
+### Root Cause
+- Profile data loader was returning `null` for users without complete profiles, and the UI was trying to read `user.name` without a safety check.
+
+### Fix
+- Used optional chaining (`user?.name`) and loaded fallback default details.

package/templates/skills/debugging/learnings.md

@@ -0,0 +1,7 @@
+# Debugging Learnings
+
+Keep track of learnings from resolved debugging sessions.
+
+## Debugging History & Tips
+
+- 

package/templates/skills/debugging/skill.md

@@ -0,0 +1,22 @@
+# Skill: Debugging
+
+Use this skill when investigating errors, broken behavior, missing UI elements, incorrect results, or failed commands.
+
+## Process
+
+1. Identify the expected behavior.
+2. Identify the actual behavior.
+3. Locate the most likely failure point.
+4. Check conditions, permissions, paths, imports, sessions, and data inputs.
+5. Propose the smallest safe fix.
+6. Include verification steps.
+
+## Common Checks
+
+- Is the condition true?
+- Is the variable defined?
+- Is the file loaded?
+- Is the query returning data?
+- Is the user allowed to see the element?
+- Is the date being treated as a string?
+- Is an old cached file being used?

package/templates/skills/documentation/examples.md

@@ -0,0 +1,9 @@
+# Documentation Examples
+
+Examples of well-formatted markdown.
+
+## Example: Inline Alerts
+Use alerts to highlight critical information:
+
+> [!IMPORTANT]
+> Always verify database credentials before deploying changes to staging or production.

package/templates/skills/documentation/learnings.md

@@ -0,0 +1,5 @@
+# Documentation Learnings
+
+History of feedback and modifications made to formatting rules.
+
+- 

package/templates/skills/documentation/skill.md

@@ -0,0 +1,19 @@
+# Skill: Documentation
+
+Use this skill when writing README files, specs, guides, implementation notes, SOPs, or handoff documents.
+
+## Process
+
+1. Identify the audience.
+2. Identify the purpose.
+3. Organize information by task or concept.
+4. Use headings and examples.
+5. Keep instructions actionable.
+6. Include assumptions and limitations.
+
+## Style
+
+- Clear.
+- Practical.
+- Structured.
+- Easy to scan.

package/templates/skills/documentation/style-guide.md

@@ -0,0 +1,8 @@
+# Style Guide
+
+Guidelines for tone, layout, and visual formatting in documents.
+
+## Markdown Guidelines
+- Always use a single `#` header per page.
+- Keep list items concise.
+- Use code fences with appropriate language markers (e.g. ` ```js `).

package/templates/skills/documentation/templates.md

@@ -0,0 +1,16 @@
+# Documentation Templates
+
+Templates for different kinds of documents.
+
+## Template: Guide / SOP
+
+```markdown
+# SOP: [Title]
+
+## Purpose
+[State the purpose of this SOP]
+
+## Step-by-Step Instructions
+1. Step 1
+2. Step 2
+```

package/templates/skills/report-generation/checklist.md

@@ -0,0 +1,9 @@
+# Report Generation Checklist
+
+Verify report correctness using the checklist below:
+
+- [ ] Is the timezone specified (e.g. UTC, EST)?
+- [ ] Are date ranges explicitly stated?
+- [ ] Are column names clear and formatted consistently?
+- [ ] Is the sorting correct?
+- [ ] Have you verified the query or source calculations?

package/templates/skills/report-generation/examples.md

@@ -0,0 +1,11 @@
+# Report Generation Examples
+
+Examples of clear report formatting.
+
+## Example: Weekly Active Users
+
+Period: 2026-06-01 to 2026-06-07 (inclusive)
+
+| Week | Active Users | Change |
+|---|---|---|
+| Week 22 | 1,420 | +12% |

package/templates/skills/report-generation/learnings.md

@@ -0,0 +1,5 @@
+# Report Generation Learnings
+
+Record learnings and feedback from reports.
+
+- 

package/templates/skills/report-generation/skill.md

@@ -0,0 +1,19 @@
+# Skill: Report Generation
+
+Use this skill when creating reports, exports, summaries, dashboards, or spreadsheet-ready outputs.
+
+## Process
+
+1. Confirm the report period.
+2. Confirm sorting direction.
+3. Identify required filters.
+4. Identify required columns.
+5. Check date boundaries.
+6. Make output easy to export or paste.
+
+## Report Rules
+
+- Always clarify whether dates are inclusive or exclusive.
+- Use real date values for sorting.
+- Use clear column names.
+- Preserve important filters.

package/templates/skills/report-generation/templates.md

@@ -0,0 +1,11 @@
+# Report Generation Templates
+
+Standard templates for dashboards and documents.
+
+## Template: CSV / Table format
+
+```markdown
+| Date | User ID | Action | Status |
+|---|---|---|---|
+| YYYY-MM-DD | 12345 | Action Name | Success |
+```

package/templates/skills/software-development/checklist.md

@@ -0,0 +1,10 @@
+# Software Development Checklist
+
+Run this checklist before submitting or approving any code changes:
+
+- [ ] Does the code build and compile without errors/warnings?
+- [ ] Are all variables, modules, and dependencies correctly imported?
+- [ ] Have you preserved existing code style and naming conventions?
+- [ ] Does it work correctly for edge cases (null inputs, empty lists, extreme values)?
+- [ ] Are secrets or config tokens properly externalized instead of hardcoded?
+- [ ] Have you tested the changes?

package/templates/skills/software-development/examples.md

@@ -0,0 +1,17 @@
+# Software Development Examples
+
+This file contains approved examples of high-quality code patterns, design solutions, and before/after diffs.
+
+## Example 1: Clear, Small Functions
+
+### Good Pattern
+Keep functions single-purpose and check inputs early:
+
+```js
+function calculateTotal(items) {
+  if (!Array.isArray(items)) {
+    throw new TypeError('Expected items to be an array');
+  }
+  return items.reduce((sum, item) => sum + (item.price * item.quantity), 0);
+}
+```

package/templates/skills/software-development/learnings.md

@@ -0,0 +1,7 @@
+# Software Development Learnings
+
+Document persistent corrections, preferences, and lessons learned from past mistakes here.
+
+## General Learnings
+
+- 

package/templates/skills/software-development/skill.md

@@ -0,0 +1,26 @@
+# Skill: Software Development
+
+Use this skill when writing, modifying, reviewing, or explaining code.
+
+## Required Inputs
+
+- Target language or framework.
+- Existing code or expected behavior.
+- Error message, if available.
+- Constraints or compatibility requirements.
+
+## Process
+
+1. Read relevant project context.
+2. Identify the exact requested change.
+3. Preserve existing behavior unless asked otherwise.
+4. Make the smallest safe change that solves the issue.
+5. Check for syntax errors and obvious runtime issues.
+6. Provide complete code or a clear replacement block.
+
+## Output Format
+
+- Explain the issue briefly.
+- Provide the fixed code.
+- Mention any assumptions.
+- Mention any follow-up checks only when needed.

package/templates/skills/software-development/templates.md

@@ -0,0 +1,19 @@
+# Software Development Templates
+
+Store common boilerplate files or standard templates here.
+
+## Template: New JavaScript Module
+
+```js
+/**
+ * Module description goes here.
+ */
+
+/**
+ * Main function.
+ * @returns {void}
+ */
+export function init() {
+  // logic here
+}
+```