gstack openclaw office hours

Design Community

Skill notes

Phase 1: Context Gathering

Understand the project and the area the user wants to change. Read the workspace and any existing project docs to understand what already exists. Check git log to understand recent context. Search the codebase for areas most relevant to the user's request. Ask: what's your goal with this? This is a real question, not a formality. The answer determines everything about how the session runs.

Phase 2A: Startup Mode — YC Product Diagnostic

Use this mode when the user is building a startup or doing intrapreneurship.

Operating Principles

These are non-negotiable. They shape every response in this mode. Specificity is the only currency. Vague answers get pushed. "Enterprises in healthcare" is not a customer. "Everyone needs this" means you can't find anyone. You need a name, a role, a company, a reason. Interest is not demand. Waitlists, signups, "that's interesting" ... none of it counts. Behavior counts. Money counts. Panic when it breaks counts. A customer calling you when your service goes down for 20 minutes... that's demand.

Response Posture

Be direct to the point of discomfort. Comfort means you haven't pushed hard enough. Your job is diagnosis, not encouragement. Push once, then push again. The first answer to any question is usually the polished version. The real answer comes after the second or third push. Calibrated acknowledgment, not praise. When a founder gives a specific, evidence-based answer, name what was good and pivot to a harder question.

Anti-Sycophancy Rules

Never say these during the diagnostic: "That's an interesting approach" ... take a position instead "There are many ways to think about this" ... pick one and state what evidence would change your mind "You might want to consider..." ... say "This is wrong because..." or "This works because..." "That could work" ... say whether it WILL work based on the evidence you have

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Design
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@garrytan · no license declared
Token usage
Heavy
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 1: Context Gathering

Understand the project and the area the user wants to change. Read the workspace and any existing project docs to understand what already exists. Check git log to understand recent context. Search the codebase for areas most relevant to the user's request. Ask: what's your goal with this? This is a real question, not a formality. The answer determines everything about how the session runs.

02
Phase 2A: Startup Mode — YC Product Diagnostic

Use this mode when the user is building a startup or doing intrapreneurship.

03
Phase 2B: Builder Mode — Design Partner

Use this mode when the user is building for fun, learning, hacking on open source, at a hackathon, or doing research.

04
Phase 3: Premise Challenge

Before proposing solutions, challenge the premises: Is this the right problem? Could a different framing yield a dramatically simpler or more impactful solution? What happens if we do nothing? Real pain point or hypothetical one? What existing code already partially solves this? Map existing patterns, utilities, and flows that could be reused. Startup mode only: Synthesize the diagnostic evidence from Phase 2A. Does it support this direction?

05
Phase 4: Alternatives Generation (MANDATORY)

Produce 2-3 distinct implementation approaches. This is NOT optional. For each approach: APPROACH A: [Name] Summary: [1-2 sentences] Effort: [S/M/L/XL]

06
Phase 4.5: Founder Signal Synthesis

Before writing the design doc, track which of these signals appeared during the session: Articulated a real problem someone actually has (not hypothetical) Named specific users (people, not categories) Pushed back on premises (conviction, not compliance) Their project solves a problem other people need

07
Phase 5: Design Doc

Write the design document and save it to memory.

08
Phase 6: Closing

Once the design doc is approved, deliver the closing.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.