humorless

flowchart TD
    I["Instructions for Claude<br/>貫穿全程的回答規範"]
    P1["1. 初始規畫<br/>web AI 對話 → SPEC.md"]
    P2["2. 開發環境<br/>CLAUDE.md、nREPL + tmux、skills、<br/>docker-compose、本地模型、假資料"]
    P3["3. Coding Agents 的開發過程<br/>每個 Phase 重複"]
    P4["4. 收尾<br/>Purpose, Rationale, Guides、Mermaid、Diataxis"]

    I -.->|"影響所有對話 (區分事實/推論)"| P1
 P1 --&gt;|"SPEC 為 Claude Code 而寫"| P2

humorless

Please scan the target codebase, identify the mechanisms and policies within it, and organize the parts worth extracting into candidate options. Once the user decides, package them into a library and refactor the original codebase.

Parameters

To be filled in by the user before execution; if left blank, ask in Phase 0.

Parameter	Description	Default
TARGET	Path of the repo to scan	Current working directory
SCOPE	Scan scope, excluding generated code and vendored code	src/; if the repo has no src/, identify the actual source directory in Phase 0 (e.g., for a Python flat layout, the top-level package, determinable from the packages setting in pyproject.toml or __init__.py); adopt and record it if it can be clearly determined, otherwise ask the user

humorless

你是一個 project instructions 生成器。

你的任務是：透過向使用者提問，收集足夠的資訊，最終生成一份「策略副手 project instructions」，讓 AI 能夠扮演該使用者公司的策略副手角色。

---

工作方式

逐區塊提問，每次問 2～3 個問題，確認回答後再繼續。不要一次把所有問題丟出去。

humorless

1. 常見指令

claude "task" ;; task
claude -p "query" ;; query
claude -c ;; continue

2. CLI 內建指令

/init
/exit

humorless

Writing Style Guide

Core Philosophy

This author writes to challenge assumptions and reveal hidden mechanisms. The writing serves as a tool for readers to see through surface phenomena and understand underlying structures—whether in debugging systems, human psychology, or business models.

---

Narrative Structure

humorless

Dev Workflow

• After editing source files, use brepl to require the changed namespace with :reload and test interactively, rather than relying solely on curl or bb test.

Interactive Development Techniques

• Call handlers directly — Ring handlers are pure functions (request map → response map). Test them in brepl without going through HTTP or middleware: (handlers/home-handler {}), (handlers/inspect-handler {}). Inspect response structure with (keys resp) before dumping the full body.
• Verify routes with Reitit — Use reitit.core/match-by-path to check route matching interactively without a browser: (reitit.core/match-by-path (reitit.ring/router app-routes/routes) "/"). Useful for verifying newly added routes before integration testing.
• Compose and inspect HoneySQL queries — Build queries incrementally as data and preview the generated SQL with (honey.sql/format query {:quoted true}) before sending to the database. This lets you verify correctness without executing a

humorless

set permission

chmod -R 777 /tmp/kestra-wd/tmp

humorless

version: 1
default_environment: dev
project_id: 019afeb1-bcc4-7481-b40a-1010c0ab4fc4
environments:
- name: dev
- name: staging
- name: prod
plugins:
  extractors:
  - name: tap-smoke-test

humorless

;; Example of using 
;;
;; -  #{...}
;; -  "&:not()"
;; -  "&:has()"

(o/defstyled form :form
...
[#{:input :textarea :select} ["&:not([type=checkbox])"
    :w-full :mb-3]]

humorless

Clojure Meetup #2

• libraries over framework
• The EDN format
• static vs dynamic types

Clojure Meetup #1

• interactive development
• tutorial