القائمة
Daily morning coaching check-in. Structured 5-question flow with pattern detection, financial runway countdown, and priority alignment check. Logs to knowledge base.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | coaching-daily |
| description | Daily morning coaching check-in. Structured 5-question flow with pattern detection, financial runway countdown, and priority alignment check. Logs to knowledge base. |
| compatibility | Requires knowledge base at ~/projects/dn-kb |
| metadata | {"author":"dandaka","version":"1.0"} |
| allowed-tools | Read, Write, Edit, Glob, Grep, AskUserQuestion, Bash(date*) |
Provide structured external accountability for personal goals. Simulate the accountability, deadlines, and stakes that make external PM work — but for personal life.
Read these files to understand current state:
~/projects/dn-kb/coaching/priorities.md — current top 3 priorities~/projects/dn-kb/profile/constraints.md — financial constraint section for runway calc~/projects/dn-kb/coaching/daily/ — find most recent file~/projects/dn-kb/profile/goals.md — for alignment checkBefore questions, display:
━━━ DAILY CHECK-IN: [date] ━━━
RUNWAY: [X] months remaining (savings / monthly deficit)
STREAK: [N] consecutive check-in days
TOP 3 PRIORITIES:
1. [Priority 1] — [status/progress note from last check-in]
2. [Priority 2] — [status/progress note]
3. [Priority 3] — [status/progress note]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Calculate runway from constraints.md financial data. Count streak from consecutive daily log files.
Use AskUserQuestion to ask these in sequence (can be batched into 2 rounds of questions):
Round 1:
Round 2: 4. Today: "What is the ONE thing that would make today a win?" — Free text 5. Alignment: "Does today's planned focus serve your #1 priority ([show priority name])?" — Yes/No/Partially
Based on answers, provide a brief coaching response. Apply these rules:
Pattern Detection (check last 5-7 daily logs):
If alignment is "No":
If alignment is "Partially":
Always end with:
Write the check-in to ~/projects/dn-kb/coaching/daily/YYYY-MM-DD.md:
# Daily Check-In: YYYY-MM-DD
## Status
- Energy: [1-5]
- Streak: [N] days
- Runway: [X] months
## Yesterday's Win
[Answer]
## Blocker
[Answer]
## Today's Focus
[ONE thing]
## Priority Alignment
[Yes/No/Partially] — [Priority #1 name]
## Coaching Notes
[Any coaching observations or pattern flags]
End with: "Have you done your 5-minute meditation today? If not, consider doing it now before starting work."
If they say yes, prompt to log it in coaching/meditation-log.md.
Use Clay for lead enrichment, prospecting, and GTM workflows. Use when finding leads, enriching companies or people, pushing data to Clay tables, or running outreach workflows. Clay is the primary enrichment platform for bracos.
Evidence-based frontend development protocol for matching a Figma source of truth to browser-rendered pixels. Ensures the project has docs/frontend-protocol.md (preflight harness checks, intent intake, measure→causal-chain→live-experiment→commit debugging modes), docs/design-vocabulary.md (shared industry design terms), and scripts/preflight.sh. Use this skill whenever the user asks to set up frontend standards, debug a layout issue, match a design or Figma artboard ("layout is off", "doesn't match the design", "pixel-perfect"), review frontend debugging practice, or when starting frontend work in a project that lacks these docs.
Ensure the current project has a docs/coding-standards.md checklist and use it to review code against the default stack (Bun, TypeScript, Drizzle, Biome, Bun-workspaces monorepo, red/green TDD) and quality principles — tidiness, separation of concerns, maintainability, stale assumptions, leftover experimental code, and doc drift. Use this skill whenever the user asks to check coding standards, review code quality, "is this tidy", "does this follow our standards", set up a coding standards doc, scaffold a new project's conventions, or before finishing/merging a change.
Interview the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.
Figma automation via the figma-use CLI (by dannote). Use when the user needs to create, modify, or inspect Figma designs programmatically. Triggers on requests to render components in Figma, sync design tokens, query or find nodes, export assets, manage variables/pages, compose screens from component instances, delta-sync web app CSS against Figma properties, or troubleshoot Figma CDP connections. Also triggers on mentions of "figma-use", "figma automation", "figma cli", "render to figma", "figma eval", or "design system sync". Never use computer-use (screenshot/click) for Figma — always use figma-use CLI.
Switch to Claude Opus 4.6 model