teach-impeccable

Name: teach-impeccable
Author: heyhank-app

30stars13forks

How to install teach-impeccable?

heyhank-app/heyhank/teach-impeccable

$npx -y skills add heyhank-app/heyhank --skill teach-impeccable

Installs into the current project.

Summary

One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.

Files · 1

View on GitHub

SKILL.md

1	Gather design context for this project, then persist it for all future sessions.
2
3	## Step 1: Explore the Codebase
4
5	Before asking questions, thoroughly scan the project to discover what you can:
6
7	- README and docs: Project purpose, target audience, any stated goals
8	- Package.json / config files: Tech stack, dependencies, existing design libraries
9	- Existing components: Current design patterns, spacing, typography in use
10	- Brand assets: Logos, favicons, color values already defined
11	- Design tokens / CSS variables: Existing color palettes, font stacks, spacing scales
12	- Any style guides or brand documentation
13
14	Note what you've learned and what remains unclear.
15
16	## Step 2: Ask UX-Focused Questions
17
18	STOP and call the AskUserQuestionTool to clarify. Focus only on what you couldn't infer from the codebase:
19
20	### Users & Purpose
21	- Who uses this? What's their context when using it?
22	- What job are they trying to get done?
23	- What emotions should the interface evoke? (confidence, delight, calm, urgency, etc.)
24
25	### Brand & Personality
26	- How would you describe the brand personality in 3 words?
27	- Any reference sites or apps that capture the right feel? What specifically about them?
28	- What should this explicitly NOT look like? Any anti-references?
29
30	### Aesthetic Preferences
31	- Any strong preferences for visual direction? (minimal, bold, elegant, playful, technical, organic, etc.)
32	- Light mode, dark mode, or both?
33	- Any colors that must be used or avoided?
34
35	### Accessibility & Inclusion
36	- Specific accessibility requirements? (WCAG level, known user needs)
37	- Considerations for reduced motion, color blindness, or other accommodations?
38
39	Skip questions where the answer is already clear from the codebase exploration.
40
41	## Step 3: Write Design Context
42
43	Synthesize your findings and the user's answers into a `## Design Context` section:
44
45	```markdown
46	## Design Context
47
48	### Users
49	[Who they are, their context, the job to be done]
50
51	### Brand Personality
52	[Voice, tone, 3-word personality, emotional goals]
53
54	### Aesthetic Direction
55	[Visual tone, references, anti-references, theme]
56
57	### Design Principles
58	[3-5 principles derived from the conversation that should guide all design decisions]
59	```
60
61	Write this section to CLAUDE.md in the project root. If the file exists, append or update the Design Context section.
62
63	Confirm completion and summarize the key design principles that will now guide all future work.

People who liked this also viewed

6 picks

Type

grill-with-docsA relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.SkillsJul 2026537k182k
lark-minutes飞书妙记：搜索妙记、查看妙记基础信息、下载/上传音视频、读取或编辑妙记的产物内容、改标题、替换说话人/关键词、申请妙记查看/编辑权限。当给出minute_token、本地音视频文件，要查/改/转妙记产物，或用户明确要主动申请妙记权限时使用；本地音视频转纪要/逐字稿优先走本 skill，不要用 ffmpeg/whisper 本地转写。不负责：获取会议关联妙记，或仅按自然语言标题定位纪要SkillsJul 2026379k16k
lark-markdown飞书 Markdown：查看、创建、上传、编辑和比较 Markdown 文件。当用户需要创建或编辑 Markdown 文件、读取、修改、局部 patch 或比较差异时使用。不负责将 Markdown 导入为飞书在线文档，也不负责文件搜索、权限、评论、移动、删除等云空间管理操作。SkillsJul 2026295k16k
docxUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', SkillsJul 2026157k163k
edit-articleSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026154k181k
lark-note飞书会议纪要（Note）直查：已知 note_id 时查询纪要详情、展示类型、关联文档 token，并读取 unified 原始逐字记录。当用户已持有 note_id，或从文档显式 vc-node-id 获得 note_id 时使用。不负责会议/日程/妙记定位、文档标题搜索或 Docx 正文读取。SkillsJul 2026154k16k

teach-impeccable

30stars13forks

View on GitHub

How to install teach-impeccable?

heyhank-app/heyhank/teach-impeccable

$npx -y skills add heyhank-app/heyhank --skill teach-impeccable

Installs into the current project.

Summary

One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.

Files · 1

View on GitHub

SKILL.md

1	Gather design context for this project, then persist it for all future sessions.
2
3	## Step 1: Explore the Codebase
4
5	Before asking questions, thoroughly scan the project to discover what you can:
6
7	- README and docs: Project purpose, target audience, any stated goals
8	- Package.json / config files: Tech stack, dependencies, existing design libraries
9	- Existing components: Current design patterns, spacing, typography in use
10	- Brand assets: Logos, favicons, color values already defined
11	- Design tokens / CSS variables: Existing color palettes, font stacks, spacing scales
12	- Any style guides or brand documentation
13
14	Note what you've learned and what remains unclear.
15
16	## Step 2: Ask UX-Focused Questions
17
18	STOP and call the AskUserQuestionTool to clarify. Focus only on what you couldn't infer from the codebase:
19
20	### Users & Purpose
21	- Who uses this? What's their context when using it?
22	- What job are they trying to get done?
23	- What emotions should the interface evoke? (confidence, delight, calm, urgency, etc.)
24
25	### Brand & Personality
26	- How would you describe the brand personality in 3 words?
27	- Any reference sites or apps that capture the right feel? What specifically about them?
28	- What should this explicitly NOT look like? Any anti-references?
29
30	### Aesthetic Preferences
31	- Any strong preferences for visual direction? (minimal, bold, elegant, playful, technical, organic, etc.)
32	- Light mode, dark mode, or both?
33	- Any colors that must be used or avoided?
34
35	### Accessibility & Inclusion
36	- Specific accessibility requirements? (WCAG level, known user needs)
37	- Considerations for reduced motion, color blindness, or other accommodations?
38
39	Skip questions where the answer is already clear from the codebase exploration.
40
41	## Step 3: Write Design Context
42
43	Synthesize your findings and the user's answers into a `## Design Context` section:
44
45	```markdown
46	## Design Context
47
48	### Users
49	[Who they are, their context, the job to be done]
50
51	### Brand Personality
52	[Voice, tone, 3-word personality, emotional goals]
53
54	### Aesthetic Direction
55	[Visual tone, references, anti-references, theme]
56
57	### Design Principles
58	[3-5 principles derived from the conversation that should guide all design decisions]
59	```
60
61	Write this section to CLAUDE.md in the project root. If the file exists, append or update the Design Context section.
62
63	Confirm completion and summarize the key design principles that will now guide all future work.

People who liked this also viewed

6 picks

Type