@stephen-lord/docs 1.0.0

package/dist/claude-code-settings/.claude-plugin/marketplace.json

@@ -0,0 +1,75 @@
+{
+  "name": "claude-code-settings",
+  "owner": {
+    "name": "Pengfei Ni"
+  },
+  "metadata": {
+    "version": "2.1.2",
+    "description": "Claude Code settings and skills for spec-driven development workflows"
+  },
+  "plugins": [
+    {
+      "name": "claude-code-settings",
+      "source": "./",
+      "description": "Claude Code settings, commands, agent and skills (all in one)",
+      "version": "2.1.1",
+      "author": {
+        "name": "Pengfei Ni"
+      }
+    },
+    {
+      "name": "kiro-skill",
+      "source": "./plugins/kiro-skill",
+      "description": "Interactive feature development workflow from idea to implementation (Requirements → Design → Tasks → Execute)",
+      "version": "1.0.0",
+      "author": {
+        "name": "Pengfei Ni"
+      }
+    },
+    {
+      "name": "spec-kit-skill",
+      "source": "./plugins/spec-kit-skill",
+      "description": "GitHub Spec-Kit integration for constitution-based spec-driven development (7-phase workflow)",
+      "version": "1.0.0",
+      "author": {
+        "name": "Pengfei Ni"
+      }
+    },
+    {
+      "name": "codex-skill",
+      "source": "./plugins/codex-skill",
+      "description": "Leverage OpenAI Codex (GPT-5/GPT-5.1) for non-interactive automation mode and hands-off task execution",
+      "version": "1.0.0",
+      "author": {
+        "name": "Pengfei Ni"
+      }
+    },
+    {
+      "name": "nanobanana-skill",
+      "source": "./plugins/nanobanana-skill",
+      "description": "Generate or edit images using Google Gemini API via nanobanana",
+      "version": "1.0.0",
+      "author": {
+        "name": "Pengfei Ni"
+      }
+    },
+    {
+      "name": "youtube-transcribe-skill",
+      "source": "./plugins/youtube-transcribe-skill",
+      "description": "Extract subtitles/transcripts from YouTube videos via CLI or browser automation",
+      "version": "1.0.0",
+      "author": {
+        "name": "Pengfei Ni"
+      }
+    },
+    {
+      "name": "autonomous-skill",
+      "source": "./plugins/autonomous-skill",
+      "description": "Use when user wants to execute long-running tasks that require multiple sessions to complete. This skill manages task decomposition, progress tracking, and autonomous execution using Claude Code headless mode with auto-continuation. Trigger phrases: autonomous, long-running task, multi-session, 自主执行, 长时任务, autonomous skill.",
+      "version": "1.0.0",
+      "author": {
+        "name": "Pengfei Ni"
+      }
+    }
+  ]
+}

package/dist/claude-code-settings/.claude-plugin/plugin.json

@@ -0,0 +1,22 @@
+{
+  "name": "claude-code-settings",
+  "version": "2.1.0",
+  "description": "Claude Code settings and skills for spec-driven development workflows",
+  "author": {
+    "name": "Pengfei Ni",
+    "url": "https://github.com/feiskyer/claude-code-settings"
+  },
+  "homepage": "https://github.com/feiskyer/claude-code-settings",
+  "repository": "https://github.com/feiskyer/claude-code-settings",
+  "license": "MIT",
+  "keywords": [
+    "copilot",
+    "litellm",
+    "kiro",
+    "spec-kit",
+    "claude-code",
+    "skills",
+    "spec-driven-development",
+    "constitution-based-development"
+  ]
+}

package/dist/claude-code-settings/.github/copilot-instructions.md

@@ -0,0 +1,96 @@
+# CLAUDE.md
+
+This file provides guidance to Claude Code and GitHub Copilot when working with code in this repository.
+
+## Environment Setup
+
+This repository contains Claude Code settings, configurations and guidance. The default setup uses GitHub Copilot as the model provider through a proxy API.
+
+### Required Dependencies
+
+- `copilot-api`: Install globally with `npm install -g copilot-api`
+- Run `copilot-api start --proxy-env` to authorize GitHub Copilot account
+- Use tmux for session management: `tmux new-session -d -s copilot 'copilot-api start --proxy-env'`
+
+### Configuration
+
+- `settings.json`: Contains environment variables for API configuration
+- Uses `localhost:4141` as the API base URL
+- Configured to use `claude-sonnet-4.5` as the primary model
+- Telemetry and non-essential traffic are disabled
+
+## Custom Commands
+
+Custom commands for Claude Code are organized in the `commands/` directory by category:
+
+### Command File Structure
+
+All command files must include YAML frontmatter with required metadata:
+
+```yaml
+---
+description: Brief description of the command
+argument-hint: [expected arguments format]
+allowed-tools: List of tools the command can use
+---
+```
+
+**Required fields:**
+
+- `description`: Clear, concise description of command purpose
+- `argument-hint`: Format showing expected arguments (e.g., `[problem or question]`)
+- `allowed-tools`: Comma-separated list of tools (e.g., `Read, Edit, Write, Bash(*)`)
+
+### Command Documentation
+
+- Command documentation belongs in `README.md` under the Commands section
+- Use collapsible `<details>` sections with clear summaries
+- Include usage examples and key features
+- Never document commands within the command files themselves
+
+### Directory Structure
+
+```sh
+commands/
+├── cc/          # Claude Code commands
+│   └── create-command.md
+└── gh/          # GitHub commands
+    └── review-pr.md
+```
+
+### Usage
+
+Run commands using the slash syntax:
+
+```sh
+/[category:][command] [ARGUMENTS]
+```
+
+**Examples:**
+
+- `/cc:create-command mycommand` - Create a new command
+- `/gh:review-pr 123` - Review pull request #123
+
+All available commands should be documented at README.md in the Commands section.
+
+### Prompt Engineering Principles
+
+When creating or modifying command prompts:
+
+- **Structure prompts systematically**: Use clear phases or sections (e.g., Analysis Phase, Execution Phase)
+- **Define specific outputs**: Include explicit output formats and structures
+- **Provide methodical approaches**: Break complex tasks into numbered steps or bullet points
+- **Include meta-cognitive elements**: Add bias awareness, assumption checking, and uncertainty assessment
+- **Balance thoroughness with conciseness**: Aim for comprehensive analysis while maintaining clarity
+- **Use progressive complexity**: Start with simple concepts and build to more complex ones
+
+### Behavioral Guidelines
+
+- **Concise communication**: Provide direct answers without unnecessary preamble or elaboration
+- **Follow existing patterns**: Always check similar commands for a consistent structure and approach
+- **Prefer editing over creating**: Always edit existing files rather than creating new ones unless absolutely necessary
+- **Use TodoWrite for complex tasks**: Track multistep processes and ensure completion of all requirements
+
+## Guidances
+
+Claude Code guidances should be put under `guidances/` directory and linked at README.md.

package/dist/claude-code-settings/.mcp.json

@@ -0,0 +1,12 @@
+{
+  "mcpServers": {
+    "chrome": {
+      "type": "stdio",
+      "command": "npx",
+      "args": [
+        "chrome-devtools-mcp@latest"
+      ],
+      "env": {}
+    }
+  }
+}

package/dist/claude-code-settings/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025-Now Pengfei Ni
+
+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.