← All skills
Tencent SkillHub Β· AI

Brainstorming

Socratic design refinement before coding. Use when user requests feature without clear spec.

skill openclawclawhub Free
0 Downloads
0 Stars
0 Installs
0 Score
High Signal

Socratic design refinement before coding. Use when user requests feature without clear spec.

⬇ 0 downloads β˜… 0 stars Unverified but indexed

Install for OpenClaw

Quick setup
  1. Download the package from Yavira.
  2. Extract the archive and review SKILL.md first.
  3. Import or place the package into your OpenClaw setup.

Requirements

Target platform
OpenClaw
Install method
Manual import
Extraction
Extract archive
Prerequisites
OpenClaw
Primary doc
SKILL.md

Package facts

Download mode
Yavira redirect
Package format
ZIP package
Source platform
Tencent SkillHub
What's included
SKILL.md

Validation

  • Use the Yavira download entry.
  • Review SKILL.md after the package is downloaded.
  • Confirm the extracted package contains the expected setup assets.

Install with your agent

Agent handoff

Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.

  1. Download the package from Yavira.
  2. Extract it into a folder your agent can access.
  3. Paste one of the prompts below and point your agent at the extracted folder.
New install

I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.

Upgrade existing

I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.

Trust & source

Release facts

Source
Tencent SkillHub
Verification
Indexed source record
Version
0.1.0

Documentation

ClawHub primary doc Primary doc: SKILL.md 7 sections Open source page

When to Use

Trigger BEFORE writing code when: User request is vague ("make it better", "add feature X") Complex feature with multiple approaches Design decisions impact multiple components

Step 1: Understand Intent

Ask clarifying questions: What problem are we solving? Who is the user? What's the success criteria? What constraints exist? (time, compatibility, dependencies)

Step 2: Explore Alternatives

Present 2-3 approaches: Approach A (simple): [description] Approach B (robust): [description] Approach C (future-proof): [description] For each: Pros, Cons, Complexity (1-5)

Step 3: Design Document

  • After user picks approach, create design doc:
  • # Feature: [Name]
  • ## Problem
  • [1-2 sentences]
  • ## Solution
  • [Chosen approach, 3-5 sentences]
  • ## Components Affected
  • [Component 1]: [Change description]
  • [Component 2]: [Change description]
  • ## Testing Strategy
  • Unit tests: [What to test]
  • Integration tests: [What to test]
  • ## Edge Cases
  • [Case 1]
  • [Case 2]
  • ## Success Criteria
  • [ ] [Criterion 1]
  • [ ] [Criterion 2]
  • Save to: docs/design/YYYY-MM-DD-feature-name.md

Step 4: Transition to Planning

Pass design doc to writing-plans skill.

Anti-Patterns

❌ Jump straight to implementation ❌ Present only one approach ❌ Skip edge case discussion ❌ Forget to save design doc

Example

User: "Add caching" Bad: I'll add Redis caching to the API. Good: Let me understand the requirements first: 1. What should be cached? (API responses, DB queries, computed results?) 2. What's the invalidation strategy? (TTL, event-based, manual?) 3. What's the acceptable staleness? (seconds, minutes, hours?) Based on your answers, I'll present 3 approaches with trade-offs.

Category context

Agent frameworks, memory systems, reasoning layers, and model-native orchestration.

Source: Tencent SkillHub

Largest current source with strong distribution and engagement signals.

Package contents

Included in package
1 Docs
  • SKILL.md Primary doc