1
---
2
name: feedback-respond-in-chinese
3
type: feedback
4
---
5

6
Always respond to this user in Chinese (中文), in every future session,
7
regardless of what language the user's own message is written in or what
8
the task is about.
9

10
Why: User explicitly requested this ("以后不管怎样都说Chinese").
11

12
How to apply: Default all user-facing text to Chinese from the very first
13
message of a session onward — don't wait for the user to switch language
14
first. This applies broadly (explanations, status updates, questions) but
15
code, commands, file contents, and technical identifiers stay in whatever
16
language/form is correct for them.

1
---
2
name: no-license-no-copy
3
type: feedback
4
---
5

6
When asked to replicate an automation script from another public repo for
7
the user's own project, the user's reasoning was "he has no license, so
8
copy his code". Pushed back and reimplemented the feature independently
9
instead of copying the source files.
10

11
Why: No LICENSE file legally defaults to "all rights reserved," not "no
12
restrictions" — public visibility on GitHub only permits viewing/forking,
13
not copying code into another project. This is the opposite of what the
14
user assumed.
15

16
How to apply: If this comes up again around reusing someone else's
17
unlicensed code, explain the no-license-means-restricted default directly
18
and offer either (a) an independent reimplementation from the described
19
behavior, or (b) asking the original author for explicit permission —
20
don't copy the source. The user accepted this once it was explained, so a
21
clear explanation is enough; no need to over-hedge.

1
---
2
name: blog-fuwari-stack
3
type: project
4
---
5

6
User's personal blog is an Astro site built from the saicaca/fuwari theme,
7
deployed to Cloudflare Pages with a custom domain. Blog niche is
8
tech/gadgets, not general life-diary content.
9

10
Deploys are manual via `wrangler pages deploy dist` after `npm run build`
11
— there is no Cloudflare Git integration connected.
12

13
Known build flake: `npm run build` intermittently fails with
14
`The 'link' class does not exist` from `src/styles/markdown.css` even when
15
`main.css` is correctly imported in `Layout.astro`. Root cause not fully
16
understood (Tailwind/Vite cache issue) — retry after
17
`rm -rf .astro node_modules/.vite node_modules/.astro dist`; sometimes
18
needs 2-3 retries or including `dist` in the clear.

1
---
2
name: project-easonza-openclaw-fork
3
type: project
4
---
5

6
The user originally asked to build a personal AI assistant gateway
7
supporting multiple model providers — the description turned out to match
8
an existing open-source project's own README almost verbatim. Rather than
9
reimplementing that project's multi-year, large-scale codebase from
10
scratch, the user chose to fork it instead.
11

12
Why: The existing open-source project (MIT licensed) already does exactly
13
what was described. Forking preserves attribution and avoids wasted effort
14
re-building existing infrastructure.
15

16
How to apply: First change was scoped narrowly and deliberately — only
17
README and package metadata, not deep internals. Full in-app rebranding
18
was explicitly scoped out as a much larger, separate effort.

1
---
2
name: reference-claude-github-app-identity
3
type: reference
4
---
5

6
The official Anthropic "Claude" GitHub identity (claude[bot]) is a
7
separate, CI-triggered integration, not something a local terminal CLI
8
session can act as.
9

10
It activates only when someone mentions @claude on a GitHub issue/PR —
11
GitHub then spins up a runner executing the official Claude Code Action
12
under the app's own identity. It has no effect on a local CLI session
13
running in a terminal — a local session's git commits always use whatever
14
git/gh account is configured on that machine.
15

16
How to apply: Don't imply or promise that a local session's future commits
17
will show as claude[bot]; correct this expectation proactively if it comes
18
up.