getting-started-guide
当用户开始新小说项目时激活 - 通过温和的提示和解释引导他们完成七步方法论(constitution → specify → clarify → plan → tasks → write → analyze)
Best use case
getting-started-guide is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
当用户开始新小说项目时激活 - 通过温和的提示和解释引导他们完成七步方法论(constitution → specify → clarify → plan → tasks → write → analyze)
Teams using getting-started-guide should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/getting-started-guide/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How getting-started-guide Compares
| Feature / Agent | getting-started-guide | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
当用户开始新小说项目时激活 - 通过温和的提示和解释引导他们完成七步方法论(constitution → specify → clarify → plan → tasks → write → analyze)
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 新用户入门引导 ## 激活条件 当用户说出以下内容时自动激活: - "我想写小说" - "我要开始一个新项目" - "怎么使用novel-writer" - "从哪里开始" --- ## 七步方法论引导 ### 欢迎消息 ``` 👋 欢迎使用Novel Writer Skills! 我注意到你要开始一个新的小说项目。 Novel Writer使用系统化的七步方法论,帮助你从想法到完稿。 让我带你快速了解流程: 第1步:/constitution - 创建创作宪法 第2步:/specify - 定义故事规格 第3步:/clarify - 澄清模糊点(5个问题) 第4步:/plan - 制定创作计划 第5步:/tasks - 分解任务清单 第6步:/write - 执行章节写作 第7步:/analyze - 质量验证分析 想要详细了解每一步吗?还是直接开始第1步? ``` ### 步骤详解(根据需要提供) ``` 【第1步:/constitution】 创建你的创作宪法 - 这是最高原则。 - 核心价值观(你想传达什么?) - 质量标准(什么算好的章节?) - 禁忌红线(不能写什么?) 为什么重要:后续所有创作都要符合宪法。 【第2步:/specify】 定义故事规格 - 明确你要写什么。 - 故事概念、类型、主题 - 目标读者、字数、结局 - 必须包含的元素(P0) 为什么重要:规格是技术需求,避免写到一半发现偏题。 【第3步:/clarify】 AI提出5个关键问题,帮你澄清模糊点。 - 针对specification中的不明确之处 - 逼迫你想清楚细节 为什么重要:模糊的规格=模糊的故事。 【第4步:/plan】 制定创作计划 - 技术方案。 - 章节架构、节奏设计 - 关键情节点时间线 - 技术难点的解决方案 为什么重要:计划详细,执行才顺畅。 【第5步:/tasks】 分解任务清单 - 可执行的步骤。 - 每个章节一个任务 - 标记状态(pending/in_progress/completed) - 追踪进度 为什么重要:大目标拆解成小任务,不overwhelm。 【第6步:/write】 执行写作 - 基于任务清单。 - 自动加载所有context - 遵循宪法、规格、计划 - 质量自检后保存 为什么重要:这是七步方法论的优势集中体现。 【第7步:/analyze】 质量验证 - 确保一致性。 - 框架检查(结构、节奏) - 内容检查(一致性、质量) - 发现问题,建议修复 为什么重要:定期分析,及时调整,避免大返工。 ``` --- ## 常见问题快速解答 ### Q: 必须按顺序执行吗? **A**: 推荐按顺序,但不强制。 ``` 推荐流程:1→2→3→4→5→6→7(循环6-7) 允许跳步: - 有经验的作者可以跳过/clarify - 短篇可以简化/plan 不推荐: - 直接跳到/write(缺少规格和计划,容易写乱) ``` ### Q: 七步走完要多久? **A**: 取决于故事复杂度。 ``` 简单故事(5万字短篇): - 步骤1-5:2-3小时 - 步骤6-7:执行写作,持续进行 复杂故事(50万字长篇): - 步骤1-5:1-2天 - 步骤6-7:数月 前期投入换来后期顺畅。 ``` ### Q: 可以中途修改吗? **A**: 当然! ``` 发现规格不对: → 修改specification.md → 重新运行/plan调整计划 计划需要调整: → 修改creative-plan.md → 更新tasks.md 这是迭代过程,不是一次定死。 ``` --- ## 第一次使用建议 ### 从简单项目开始 ``` ✓ 推荐: - 5-10万字的中短篇 - 单一类型(言情/悬疑/历史) - 简单情节(1-2条主线) ⚠️ 不推荐初次就写: - 50万字+的长篇 - 多类型融合(如言情+悬疑+奇幻+历史) - 超复杂世界观 先熟悉流程,再挑战复杂项目。 ``` ### 执行第一个命令 ``` 准备好了?让我们开始第1步: 执行命令:/constitution 我会引导你创建创作宪法。 准备回答以下问题: 1. 这个故事你想传达什么核心理念? 2. 你对质量的标准是什么? 3. 有哪些内容是绝对不能写的? 准备好了就输入:/constitution ``` --- ## 与workflow-guide的配合 ``` getting-started: - 初次使用时激活 - 提供完整流程概览 - 回答入门问题 workflow-guide: - 整个创作过程中持续激活 - 偏离流程时温和提醒 - 提供最佳实践建议 两者互补: getting-started = 入门教程 workflow-guide = 持续顾问 ``` --- ## 总结 getting-started-guide = 你的**入门向导** ✓ 自动识别新用户 ✓ 引导七步方法论 ✓ 回答常见问题 ✓ 给出第一步建议 **让第一次使用不再迷茫!** 🚀 --- **本Skill版本**: v1.0 **最后更新**: 2025-10-18
Related Skills
novel-writer-workflow-guide
Use when user starts a novel project or asks how to organize their writing - guides through novel-writer's seven-step methodology and ensures proper workflow
component-guidelines-docs
Generate comprehensive component guideline documentation for SEED Design System. Use when creating or updating design guideline documentation in ./docs/content/docs/components directory. This skill helps create high-quality documentation similar to action-button.mdx.
Claudeisms Operational Guidelines
Apply strict operational protocols for AI task execution including sequential processing, minimal responses, no destructive operations without confirmation
brand-guidelines
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
backend-dev-guidelines
Comprehensive backend development guide for Langfuse's Next.js 14/tRPC/Express/TypeScript monorepo. Use when creating tRPC routers, public API endpoints, BullMQ queue processors, services, or working with tRPC procedures, Next.js API routes, Prisma database access, ClickHouse analytics queries, Redis queues, OpenTelemetry instrumentation, Zod v4 validation, env.mjs configuration, tenant isolation patterns, or async patterns. Covers layered architecture (tRPC procedures → services, queue processors → services), dual database system (PostgreSQL + ClickHouse), projectId filtering for multi-tenant isolation, traceException error handling, observability patterns, and testing strategies (Jest for web, vitest for worker).
backend-ai-guide
|
applying-brand-guidelines
This skill applies consistent corporate branding and styling to all generated documents including colors, fonts, layouts, and messaging
zapier-workflows
Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to "run" any process. Also handles Perplexity-based research and Google Sheets data tracking.
writing-skills
Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dependencies, and rust-documentation skills.
writing-plans
Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge
workflow-orchestration-patterns
Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running processes, distributed transactions, or microservice orchestration.
workflow-management
Create, debug, or modify QStash workflows for data updates and social media posting in the API service. Use when adding new automated jobs, fixing workflow errors, or updating scheduling logic.