Communitygithub.com

cdcoonce/Portfolio_Website

使用并行子代理生成多个根本不同的模块界面设计方案。当用户想要设计API、探索界面选项、比较模块形态或提到“设计两次”时使用。

Portfolio_Website 是什么?

该技能基于《软件设计哲学》中的“设计两次”原则,帮助开发者通过并行生成多个截然不同的接口设计方案,避免过早陷入单一思路。它首先引导用户收集需求,然后利用任务工具同时派生出3个以上的子代理,每个子代理都遵循不同的约束(例如最小化方法数量、最大化灵活性或针对最常见情况进行优化)来生成独立的接口提案。每个方案都会以接口签名、使用示例、隐藏的复杂性及权衡分析的形式呈现。随后,用户将有机会逐一审视各个设计,并从接口简洁性、通用性、实现效率、深度(即小接口隐藏复杂逻辑)以及易用性等维度进行比较。最终,用户可以将不同设计中的优点进行综合,形成更优的融合方案。该技能支持在Claude Code等AI代理平台中使用,旨在促进更理性、更系统的软件架构决策。

兼容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/cdcoonce/Portfolio_Website/tree/HEAD/.claude/skills/design-an-interface

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档

设计接口

基于《软件设计哲学》中的“设计两次”原则:你的第一个想法不太可能是最好的。生成多个根本不同的设计,然后进行比较。

工作流程

1. 收集需求

在设计之前,请先理解:

  • 这个模块要解决什么问题?
  • 调用者是谁?(其他模块、外部用户、测试)
  • 关键操作有哪些?
  • 有任何约束吗?(性能、兼容性、现有模式)
  • 哪些应该隐藏在内部,哪些应该暴露?

问:“这个模块需要做什么?谁会使用它?”

2. 生成设计(并行子代理)

使用 Task 工具同时派生出 3 个以上的子代理。每个子代理必须生成一种根本不同的方法。

每个子代理的提示模板:

为以下模块设计接口:[模块描述]

需求:[收集的需求]

此设计的约束条件:[为每个代理分配不同的约束条件]
- 代理 1:“最小化方法数量 - 目标最多 1-3 个方法”
- 代理 2:“最大化灵活性 - 支持多种用例”
- 代理 3:“针对最常见情况进行优化”
- 代理 4:“从 [特定范式/库] 中汲取灵感”

输出格式:
1. 接口签名(类型/方法)
2. 使用示例(调用者如何使用)
3. 此设计内部隐藏了什么
4. 这种方法的权衡

3. 展示设计

展示每个设计,包括:

  1. 接口签名 - 类型、方法、参数
  2. 使用示例 - 调用者在实际中如何使用
  3. 隐藏的内容 - 维持内部的复杂性

按顺序展示设计,以便用户在比较之前能够吸收每个方法。

4. 比较设计

在展示所有设计之后,从以下方面进行比较:

  • 接口简洁性:方法更少、参数更简单
  • 通用与专用:灵活性 vs 专注
  • 实现效率:形态是否允许高效内部实现?
  • 深度:小接口隐藏大量复杂性(好) vs 大接口但实现单薄(差)
  • 正确使用的容易程度 vs 误用的风险

用文字而非表格讨论权衡。重点标出设计之间最大的分歧点。

5. 综合

通常,最佳设计来自多个选项见解的结合。询问:

  • “哪个设计最适合你的主要用例?”
  • “是否有其他设计中的元素值得纳入?”

评估标准

来自《软件设计哲学》:

接口简洁性:方法越少、参数越简单 = 更容易学习和正确使用。

通用性:无需修改即可处理未来用例。但需警惕过度泛化。

实现效率:接口形态是否允许高效实现?还是导致内部实现笨拙?

深度:小接口隐藏大量复杂性 = 深模块(好)。大接口但实现单薄 = 浅模块(避免)。

反模式

  • 不要允许子代理产生相似的设计 - 强制实现根本差异
  • 不要跳过比较 - 价值在于对比
  • 不要实现 - 这纯粹是接口形态设计
  • 不要根据实现工作量来评估

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

cdcoonce/Portfolio_Website

Git commit workflow with enforced conventional commit style. Use when Claude needs to stage and commit changes, craft commit messages, or the user asks to commit, make a commit, or save their work. Ensures consistent commit message format, proper scoping, and atomic commits across the project.

cdcoonce/Portfolio_Website

AI-powered code quality analysis for Python, Markdown, and Mermaid diagrams. Use this skill when: (1) reviewing code for quality issues, (2) checking Python files for PEP8 violations, unused code, missing type hints, docstring problems, complexity issues, or potential runtime errors, (3) validating Markdown documentation for broken links, heading structure, or formatting issues, (4) validating Mermaid diagram syntax, (5) the user asks for a "code review" or "quality check", (6) analyzing code snippets pasted in conversation, or (7) suggesting and applying fixes for code quality issues.

cdcoonce/Portfolio_Website

Deploy the portfolio chat agent Lambda function to AWS. Use when the user asks to deploy, redeploy, push to Lambda, update the chat agent, or after updating context files or lambda_function.py. Rebuilds the knowledge base, packages dependencies, and deploys to AWS Lambda.

cdcoonce/Portfolio_Website

Orchestrate the full GitHub-issues-driven development lifecycle. 7-phase pipeline from brainstorm through PR with state tracking and cross-conversation resume. Use when user says "dev cycle", "development workflow", "full development pipeline", or invokes /dev-cycle.

cdcoonce/Portfolio_Website

Production Python coding standards with automatic version detection (3.10-3.13). Use when writing, reviewing, or refactoring Python to ensure adherence to modern type syntax, LBYL exception handling, pathlib operations, ABC-based interfaces, and production-tested patterns. Not Dagster-specific - applies to any Python project.

cdcoonce/Portfolio_Website

Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.

cdcoonce/Portfolio_Website

GitHub CLI (gh) integration for managing issues, pull requests, branches,

cdcoonce/Portfolio_Website

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

cdcoonce/Portfolio_Website

Explore a codebase to find opportunities for architectural improvement, focusing on making the codebase more testable by deepening shallow modules. Use when user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more AI-navigable.

cdcoonce/Portfolio_Website

CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Three modes: SCOPE EXPANSION (dream big), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials). Use when the user asks for a plan review, CEO review, mega review, or wants a plan challenged/stress-tested before implementation.

cdcoonce/Portfolio_Website

Break a PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. Use when user wants to convert a PRD to issues, create implementation tickets, or break down a PRD into work items.

cdcoonce/Portfolio_Website

Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in docs/plans/. Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets".

cdcoonce/Portfolio_Website

Generate or update the `.claude/docs/project.md` file that gives Claude project-specific context. Use this skill when the user asks to create, update, regenerate, or refresh project context, or says things like "update project.md", "generate project context", "this repo needs a project.md", or "Claude doesn't know about this project". Also trigger when onboarding Claude to a new repository for the first time.

cdcoonce/Portfolio_Website

Generate comprehensive, high-quality README.md files for code repositories. Use this skill whenever the user asks to create, write, generate, update, or improve a README for any project or repository. Also trigger when the user says things like "document this project", "write docs for this repo", "this repo needs a README", "help me onboard developers to this codebase", or asks for project documentation in markdown. Even if the user just says "README" or "readme" in the context of a codebase, use this skill.

cdcoonce/Portfolio_Website

Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.

cdcoonce/Portfolio_Website

Set up pre-commit hooks for the current repo. Use when user wants to add pre-commit hooks, configure commit-time linting, formatting, type checking, or testing. Triggers on "pre-commit", "git hooks", "linting hooks", or /setup-pre-commit.

cdcoonce/Portfolio_Website

Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.

cdcoonce/Portfolio_Website

Triage a bug or issue by exploring the codebase to find root cause, then create a GitHub issue with a TDD-based fix plan. Use when user reports a bug, wants to file an issue, mentions "triage", or wants to investigate and plan a fix for a problem.

cdcoonce/Portfolio_Website

Rewrites the prose sections of wiki pages in-place. Reads source files to understand current context, then updates only the content inside <!-- claude:prose --> ... <!-- claude:prose:end --> markers. Never touches <!-- generated:start --> ... <!-- generated:end --> blocks. Supports targeting a single page with /update-wiki {PageName}.

cdcoonce/Portfolio_Website

Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.

相关技能