@dedesfr/prompter 0.8.7 → 0.8.9

package/src/commands/init.ts

@@ -70,6 +70,67 @@ export class InitCommand {
         return choices;
     }
 
+    private getCategorizedSkillChoices(availableSkills: SkillMetadata[], currentSkillNames: string[]): any[] {
+        const categories = [
+            {
+                name: '📋 Planning & Strategy',
+                skills: ['project-orchestrator', 'feature-planner', 'prompter-workflow', 'prompter-specs']
+            },
+            {
+                name: '🎨 Design & UI/UX',
+                skills: ['ui-ux-pro', 'design-system-generator', 'design-md']
+            },
+            {
+                name: '⚙️ Development & Code Review',
+                skills: ['code-review', 'laravel-code-review', 'mcp-builder']
+            },
+            {
+                name: '📝 Documentation',
+                skills: ['doc-builder', 'document-translator', 'agents-md-generator', 'meeting-notes']
+            },
+            {
+                name: '✨ Content & Productivity',
+                skills: ['gamma-builder', 'enhance-prompt']
+            }
+        ];
+
+        const categorized = new Set<string>();
+        const choices: any[] = [];
+
+        for (const category of categories) {
+            const skillsInCategory = category.skills
+                .map(name => availableSkills.find(s => s.name === name))
+                .filter((s): s is SkillMetadata => !!s);
+
+            if (skillsInCategory.length === 0) continue;
+
+            choices.push(new Separator(chalk.bold.cyan(category.name)));
+            for (const skill of skillsInCategory) {
+                categorized.add(skill.name);
+                choices.push({
+                    name: `  ${skill.name}`,
+                    value: skill.name,
+                    checked: currentSkillNames.includes(skill.name)
+                });
+            }
+        }
+
+        // Uncategorized skills
+        const uncategorized = availableSkills.filter(s => !categorized.has(s.name));
+        if (uncategorized.length > 0) {
+            choices.push(new Separator(chalk.bold.cyan('🔧 Other')));
+            for (const skill of uncategorized) {
+                choices.push({
+                    name: `  ${skill.name}`,
+                    value: skill.name,
+                    checked: currentSkillNames.includes(skill.name)
+                });
+            }
+        }
+
+        return choices;
+    }
+
     async execute(options: InitOptions = {}): Promise<void> {
         const projectPath = process.cwd();
         const isReInitialization = await PrompterConfig.prompterDirExists(projectPath);
@@ -177,11 +238,8 @@ export class InitCommand {
 
                 const selectedSkillNames = await checkbox({
                     message: 'Select skills to install:',
-                    choices: availableSkills.map(skill => ({
-                        name: `  ${skill.name}`,
-                        value: skill.name,
-                        checked: currentSkillNames.includes(skill.name)
-                    }))
+                    choices: this.getCategorizedSkillChoices(availableSkills, currentSkillNames),
+                    pageSize: 20
                 });
                 selectedSkills = availableSkills.filter(s => selectedSkillNames.includes(s.name));
             } catch (error) {

package/docs/product-spec.md

@@ -1,151 +0,0 @@
-Product Specification Document
-
-### 1. Executive Summary
-- Product name and tagline: **Prompter CLI** — “Enhance prompts directly in your AI coding workflow.”
-- Core value proposition: Turn rough ideas into **structured, professional prompt specifications** and install tool-specific slash-command workflows in local repos.
-- Primary target users: Developers/teams using AI coding assistants who want standardized prompt enhancement workflows.
-- Key differentiators: **Multi-tool workflow generation**, **local-first** (filesystem-only), and **managed template updates** using embedded markers.
-
-### 2. Product Overview
-- **Problem Statement:** AI prompt quality is inconsistent; teams need a repeatable way to transform rough ideas into high-quality specs and make them available as slash commands in their tools.
-- **Solution:** A CLI that initializes a project with Prompter context, generates slash-command workflow files for supported AI tools, and helps list enhanced prompts.
-- **Success Metrics:**
-  - Successful initialization rate (`prompter init` completes).
-  - Number of workflow files created/updated.
-  - Number of enhanced prompts listed (`prompter list` output count).
-- **Scope:**
-  - **Included:** CLI commands (`init`, `update`, `list`), file templates for workflows, project context file, and detection of enhanced prompts.
-  - **Excluded:** Actual prompt enhancement execution (done by the AI tool), remote services, authentication, telemetry.
-
-### 3. User Personas
-- **Primary: AI-Enabled Developer**
-  - Goals: Quickly bootstrap AI prompt workflows; keep workflows up to date.
-  - Pain points: Inconsistent prompt specs; manual setup across tools.
-- **Secondary: Team Lead/Architect**
-  - Goals: Standardize AI prompt practices across team repos.
-  - Pain points: Tool fragmentation and drift in prompt instructions.
-- **Use Case Scenarios:**
-  - New repo bootstrap → run `prompter init` to scaffold workflows.
-  - Existing repo update → run `prompter update` to refresh managed sections.
-  - Review prompt history → run `prompter list` to see enhanced specs.
-
-### 4. Feature Specifications
-
-**Feature Name:** CLI Initialization
-- **Description:** Creates `prompter/` directory, `prompter/project.md`, optional `AGENTS.md`, and tool-specific workflow files.
-- **User Flow:**
-  1. User runs `prompter init`.
-  2. CLI checks if `prompter/` exists; if so, exits with warning.
-  3. User selects tools (interactive checkbox) or passes `--tools`.
-  4. CLI writes templates and workflow files.
-  5. CLI prints next steps.
-- **Acceptance Criteria:**
-  - `prompter/` directory created with `project.md`.
-  - `AGENTS.md` created only if missing.
-  - Tool workflow files created under tool-specific paths.
-  - Success message printed.
-- **Priority:** Critical
-- **Dependencies:** `src/commands/init.ts`, `src/core/config.ts`, templates in `src/core/templates/*`, configurators in `src/core/configurators/slash/*`.
-
-**Feature Name:** Workflow Update
-- **Description:** Updates managed template sections in existing workflow files for all supported tools.
-- **User Flow:**
-  1. User runs `prompter update`.
-  2. CLI checks for `prompter/`; if missing, exits with error.
-  3. For each tool configurator, updates files containing managed markers.
-  4. Outputs updated count.
-- **Acceptance Criteria:**
-  - If `prompter/` absent, prints error and sets exit code.
-  - If managed markers missing, logs failure for that file.
-  - Updates only managed section between markers.
-- **Priority:** High
-- **Dependencies:** `src/commands/update.ts`, `src/core/configurators/slash/base.ts`, `src/core/config.ts`.
-
-**Feature Name:** Enhanced Prompt Listing
-- **Description:** Lists existing enhanced prompts under `prompter/<slug>/enhanced-prompt.md`.
-- **User Flow:**
-  1. User runs `prompter list` (or `--json`).
-  2. CLI scans `prompter/` for directories containing `enhanced-prompt.md`.
-  3. Outputs list and optional JSON structure.
-- **Acceptance Criteria:**
-  - JSON output when `--json` used.
-  - Empty state messaging when no prompts found.
-  - Sorted list by slug.
-- **Priority:** Medium
-- **Dependencies:** `src/commands/list.ts`, `src/core/config.ts`.
-
-**Feature Name:** Tool-Specific Workflow Generation
-- **Description:** Creates or updates slash-command files for supported AI tools.
-- **User Flow:**
-  1. CLI picks tool configurator based on user selection.
-  2. Writes file with frontmatter (if applicable) and managed markers.
-- **Acceptance Criteria:**
-  - Files created under correct tool paths.
-  - Body contains managed markers from `PROMPTER_MARKERS`.
-- **Priority:** High
-- **Dependencies:** `src/core/configurators/slash/*`, `src/core/templates/slash-command-templates.ts`.
-
-### 5. Technical Architecture
-- **System Overview:** Local CLI that reads/writes repository files and generates prompt templates. No server-side components.
-- **Technology Stack:**
-  - **Language:** TypeScript → compiled to Node.js ES Modules (`src/` → `dist/`).
-  - **Runtime:** Node.js >= 20 (`package.json`).
-  - **Libraries:** `commander`, `@inquirer/prompts`, `chalk`.
-- **Data Models:**
-  - `EnhancedPrompt` (in-memory): `{ id, path, createdAt }` in `src/commands/list.ts`.
-  - `ToolChoice` and `SUPPORTED_TOOLS` in `src/core/config.ts`.
-- **APIs & Integrations:** No network APIs. Integrates with tool-specific file conventions.
-- **Infrastructure:** Local filesystem only. CLI entry is `bin/prompter.js` which loads `dist/cli/index.js`.
-
-**Architecture Diagram (Mermaid):**
-```mermaid
-flowchart TD
-  CLI[prompter CLI] -->|init| FS[(Local Filesystem)]
-  CLI -->|update| FS
-  CLI -->|list| FS
-  FS -->|workflow files| Tools[AI Tools: Claude/Codex/etc.]
-  Templates[Templates] --> CLI
-```
-
-### 6. Non-Functional Requirements
-- **Performance:** Fast file IO; scans only `prompter/` directory.
-- **Security:** No authentication; operates on local filesystem; no data transmission.
-- **Scalability:** Handles many prompt folders; linear scan in `prompter/`.
-- **Reliability:** Uses guarded checks for existing directories; safe updates via marker boundaries.
-- **Compliance:** None specified. ⚠️ ASSUMPTION: Local-only operation minimizes compliance needs.
-
-### 7. User Interface Specifications
-- **Navigation Structure:** CLI commands:
-  - `prompter init`
-  - `prompter update`
-  - `prompter list`
-- **Key Screens/Pages:** Terminal output with colored status messages (`chalk`).
-- **Design Patterns:**
-  - Interactive selection via checkbox prompt.
-  - Managed template sections via markers: `<!-- prompter-managed-start -->` and `<!-- prompter-managed-end -->`.
-- **Responsive Behavior:** N/A (CLI).
-
-### 8. Integration Requirements
-- **Third-Party Services:** None.
-- **APIs Consumed:** None.
-- **APIs Provided:** CLI commands only.
-- **Webhooks/Events:** None.
-
-### 9. Data Specifications
-- **Data Models:**
-  - `prompter/project.md` — project context template.
-  - Workflow files per tool, e.g., `.codex/prompts/prompter-enhance.md`.
-- **Data Flow:** User input → CLI templates → filesystem output → AI tool reads workflow file.
-- **Storage Requirements:** Low; markdown text files only.
-- **Data Privacy:** No PII processing; files are local. ⚠️ ASSUMPTION: Enhanced prompts may include sensitive text, handled by repo policies.
-
-### 10. Current Limitations & Technical Debt
-- No validation of `--tools` inputs; invalid tool IDs are ignored silently (no error path in `src/commands/init.ts`).
-- `prompter update` updates all known tools, even if not used in the project.
-- No tests present (no `test/` files found).
-- Update requires markers; files without them error (`src/core/configurators/slash/base.ts`).
-
-### 11. Assumptions & Inferences
-- ⚠️ ASSUMPTION: Prompter is intended to be used as a **global CLI** (`npm install -g`), inferred from README and `package.json` `bin` mapping.
-- ⚠️ ASSUMPTION: Enhanced prompts are generated by the AI assistant following the workflow, not by this CLI.
-- ⚠️ ASSUMPTION: Users will maintain versioned workflow files in their repos and accept managed updates.

package/docs/tasks.md

@@ -1,3 +0,0 @@
-COMMAND_NAME = ['apply', 'archive', 'proposal']
-
-i want to add new command for {COMMAND_NAME}. you can check the prompt in prompt folder here with name match {COMMAND_NAME}.md

package/skills/skill-creator/LICENSE.txt

@@ -1,202 +0,0 @@
-
-                                 Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
-
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-   1. Definitions.
-
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
-
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
-
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
-
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
-
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
-
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
-
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
-
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
-
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to Licensor for inclusion in the Work by the copyright owner
-      or by an individual or Legal Entity authorized to submit on behalf of
-      the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
-
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
-
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
-
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
-
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
-
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
-
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
-
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
-
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
-
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
-
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
-
-   6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
-
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
-
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
-
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.
-
-   END OF TERMS AND CONDITIONS
-
-   APPENDIX: How to apply the Apache License to your work.
-
-      To apply the Apache License to your work, attach the following
-      boilerplate notice, with the fields enclosed by brackets "[]"
-      replaced with your own identifying information. (Don't include
-      the brackets!)  The text should be enclosed in the appropriate
-      comment syntax for the file format. We also recommend that a
-      file or class name and description of purpose be included on the
-      same "printed page" as the copyright notice for easier
-      identification within third-party archives.
-
-   Copyright [yyyy] [name of copyright owner]
-
-   Licensed under the Apache License, Version 2.0 (the "License");
-   you may not use this file except in compliance with the License.
-   You may obtain a copy of the License at
-
-       http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing, software
-   distributed under the License is distributed on an "AS IS" BASIS,
-   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-   See the License for the specific language governing permissions and
-   limitations under the License.