TOOLS.md - Local Notes

Skills define how tools work. This file is for your specifics β€” the stuff that’s unique to your setup.

Git

All commits must use Adam’s GitHub account:

  • Name: Chaoticonomist
  • Email: 17127489+Chaoticonomist@users.noreply.github.com

This is required for Vercel deployments to work (they reject commits without a linked GitHub author).

What Goes Here

Things like:

  • Camera names and locations
  • SSH hosts and aliases
  • Preferred voices for TTS
  • Speaker/room names
  • Device nicknames
  • Anything environment-specific

Examples

### Cameras
- living-room β†’ Main area, 180Β° wide angle
- front-door β†’ Entrance, motion-triggered
 
### SSH
- home-server β†’ 192.168.1.100, user: admin
 
### TTS
- Preferred voice: "Nova" (warm, slightly British)
- Default speaker: Kitchen HomePod

Why Separate?

Skills are shared. Your setup is yours. Keeping them apart means you can update skills without losing your notes, and share skills without leaking your infrastructure.


Installed Skills (2026-02-10)

Browser & Scraping

  • browser-automation β€” Natural language browser control (browser navigate, browser act)
  • stagehand-browser-cli β€” Same as above, Stagehand-based
  • playwright-scraper-skill β€” Heavy-duty scraping with anti-bot bypass
    • Location: /root/clawd/skills/playwright-scraper-skill/
    • Use playwright-stealth.js for Cloudflare-protected sites
    • Already set up: npm install + npx playwright install chromium βœ…

Productivity & Self-Improvement

  • proactive-agent β€” WAL protocol, working buffer, relentless resourcefulness
  • recursive-self-improvement β€” Fix/optimize cycles for codebases
  • focus-deep-work β€” Pomodoro, distraction logging, focus stats

Frontend

  • frontend-design-ultimate β€” Anti-AI-slop web design
    • Stack: React + Tailwind + shadcn/ui + Framer Motion
    • Banned: Inter, Roboto, solid white backgrounds
    • Use for: CalWizz refresh, new landing pages

Drafts Naming Convention

Format: {project}-{type}-{description}.md

Projects

  • calwizz β€” Calendar analytics app
  • truebabycost β€” Baby product comparison site
  • changelog β€” Chainlog (change audit SaaS)
  • system β€” Cross-project or infrastructure

Types (General)

  • blog β€” Blog post content
  • tweets β€” Tweet drafts/threads
  • spec β€” Feature specifications
  • audit β€” Quality/performance audits
  • review β€” Code/content reviews
  • doc β€” Documentation
  • guide β€” How-to guides
  • plan β€” Strategy/roadmap documents
  • research β€” Research notes
  • data β€” Data files/exports
  • emails β€” Email templates
  • templates β€” Reusable templates
  • brief β€” Creative briefs

Blog Post Tags (Frontmatter)

Add to YAML frontmatter in blog posts:

---
title: "Post Title"
tags: [compare, calwizz]
---

Content Tags:

  • compare β€” vs competitor comparisons
  • guide β€” how-to, educational content
  • opinion β€” thought leadership, hot takes
  • product β€” feature/product announcements
  • research β€” data-driven insights
  • listicle β€” numbered lists/tips

Project Tags:

  • calwizz, truebabycost, changelog

Twitter/X Content Management

History files (one per account/project):

  • drafts/tweets-history-shippingshovels.md β€” @ShippingShovels (builder, general)
  • drafts/tweets-history-calwizzapp.md β€” @CalWizzApp (product)
  • drafts/tweets-history-truebabycost.md β€” @ShippingShovels (True Baby Cost content)

Workflow:

  1. Before drafting: Review that account’s history file to avoid repetitive hooks/themes
  2. Draft: Add new tweets to the Queue section
  3. After posting: Move from Queue β†’ Posted with date

Future: Pull posted tweets directly from X API to backfill history.

Posting times: 9:00 AM ET weekdays for B2B content


Add whatever helps you do your job. This is your cheat sheet.