By hironow
Autonomous web design exploration plugin. Iteratively explores design variations under quality constraints using git-based keep/revert cycles, inspired by autoresearch.
Analyze results from an autodesign exploration loop. This skill should be used when the user asks to "analyze design results", "show design progress", "summarize design exploration", "what designs worked", "design statistics", "which exploration axis performed best", or needs to review the results from design-results.tsv.
Core methodology reference for the autodesign keep/revert cycle. This skill provides the rules, decision logic, and error recovery patterns for the autonomous loop — not the top-level entry point (use /design for that). Applicable when the user asks about "autodesign pattern", "keep/revert logic", "design decision criteria", "design exploration strategy", "run keep/revert design optimization", or needs guidance on how the autonomous explore-evaluate-decide cycle works internally.
This skill should be used when the user asks to "start design exploration", "run autonomous design", "explore design variations", "optimize my design", "begin design loop", "run autodesign", or needs to start or resume an autonomous web design exploration loop. This is the top-level entry point that orchestrates setup and loop execution. For internal keep/revert methodology, see the design-loop skill.
This skill should be used when the user asks to "set up a design experiment", "initialize a design exploration", "create design config", "prepare design branch", or needs to configure the autodesign environment before starting an autonomous design exploration loop.
Modifies files
Hook triggers on file write and edit operations
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
My configuration for Zsh, Mise, Just, and more.
Requires curl and git.
bash -c "$(curl -fsSL https://raw.githubusercontent.com/hironow/dotfiles/main/install.sh)"
[!NOTE]
Mac, Linux, Windows(WSL内Linux)へ対応
# just (task runner)
just help
just sync-agents-preview
just sync-agents
just update-all
just dump
# diagnostics
just self-check
# run with quick validate tests (needs Docker)
just self-check with_tests=1
just doctor
just validate-path-duplicates
# uv on mise
mx uv sync
# just on mise
mx just --list
# mise env
mx dotenvx run -- mise set
# mise env with github credentials (use gh extension)
gh do -- mise set
# set env by dotenvx (encrypted)
mx dotenvx set HELLO World
# set env by mise (plain, unencrypted)
mx mise set WORLD=hello
# run all sandbox tests
just test
# run by pytest marker (install/validate/versions/deploy/check)
just test-mark marker=validate
# verify install.sh (docker required)
just test-install
# full install
bash ./install.sh
# lightweight (skip heavy tools)
INSTALL_SKIP_HOMEBREW=1 INSTALL_SKIP_GCLOUD=1 INSTALL_SKIP_ADD_UPDATE=1 bash ./install.sh
# check A record for localhost -> 127.0.0.1
dig localhost.hironow.dev
# create/update cert for https
sudo certbot certonly --manual --preferred-challenges dns -d localhost.hironow.dev --config-dir ${config_root}/private/certificates
# check simple-server for https localhost
cd tools/simple-server
sudo mise x -- go run main.go
claude mcp add -s user chrome-devtools bunx chrome-devtools-mcp@latest
claude mcp add -s user -t http deepwiki https://mcp.deepwiki.com/mcp
# latest documentation MCP per user
claude mcp add -s user -t http bun https://bun.com/docs/mcp
claude mcp add -s user -t http cloudflare https://docs.mcp.cloudflare.com/mcp
claude mcp add -s user -t http vercel https://mcp.vercel.com
claude mcp add -s user -t http livekit-docs https://docs.livekit.io/mcp
claude mcp add -s user -t http openai https://developers.openai.com/mcp
# -- Google Cloud: https://developers.google.com/knowledge/mcp#gcloud-cli
YOUR_PROJECT_ID=<your-project-id>
gcloud beta services mcp enable developerknowledge.googleapis.com --project=$YOUR_PROJECT_ID
# -- needs credentials setup
# gcloud auth login
# gcloud auth application-default login
gcloud services api-keys create --project=$YOUR_PROJECT_ID --display-name="DK API Key"
YOUR_API_KEY=<your-keyString>
claude mcp add google-dev-knowledge -s user -t http https://developerknowledge.googleapis.com/mcp --header "X-Goog-Api-Key: $YOUR_API_KEY"
# -- AWS: https://awslabs.github.io/mcp/servers/aws-knowledge-mcp-server/
claude mcp add -s user -t http aws-knowledge-mcp-server https://knowledge-mcp.global.api.aws
# -- k6: https://grafana.com/docs/k6/latest/release-notes/v1.6.0/#introducing-mcp-k6-ai-assisted-k6-script-writing-mcp-k6
claude mcp add --scope=user --transport=stdio k6 -- docker run --rm -i grafana/mcp-k6
# specific (needs copy for other agents' directory) per project
claude mcp add -s project -t http jaeger http://localhost:16687/mcp
MCP catalog refs.
justfile経由で CLAUDE_CONFIG_DIR を切り替えつつ操作できる:
just skills ls # デフォルトconfigでスキル一覧
just skills add <repo> --all # スキル追加
just env=a skills ls -g # ~/.claude-work-a 向け
just env=b skills ls -g # ~/.claude-work-b 向け
just env=c skills ls -g # ~/.claude-work-c 向け
just env=d skills ls -g # ~/.claude-work-d 向け
just env=p skills ls -g # ~/.claude (personal) 向け
just skills add vercel-labs/agent-skills
just skills add modelcontextprotocol/ext-apps
just skills add wandb/skills
just skills add https://github.com/googleworkspace/cli
# browser: https://github.com/vercel-labs/agent-browser?tab=readme-ov-file#agentsmd--claudemd
just skills add vercel-labs/agent-browser
Skill catalog refs.
# avoid merge commits when pulling
git config --global pull.rebase true
npx claudepluginhub hironow/dotfiles --plugin autodesignAutonomous experiment loop plugin inspired by karpathy/autoresearch. Iteratively modifies target code, evaluates against fixed metrics, and keeps only improvements via git-based keep/revert cycles.
Agents for UI/UX design, accessibility, and user experience optimization
Transform Claude Code into a structured development platform with 29 /sc: commands, 23 specialized agents, 7 behavioral modes, and MCP server integration
Build FastMCP 3.x Python MCP servers — covers provider/transform architecture (including CodeMode, Tool Search, and server-level transforms), component versioning, session state, authorization (MultiAuth, PropelAuth, connection-pooled token verifiers), evaluation creation, Pydantic validation, async patterns, STDIO and HTTP transports, nginx reverse proxy deployment, background tasks, Prefab Apps UI, security patterns, client SDK usage, testing, deployment, and migration from FastMCP v2. TypeScript is a legacy reference only and is not updated for v3.
MCP servers for Codex integration
Complete collection of battle-tested Claude Code configs from an Anthropic hackathon winner - agents, skills, hooks, and rules evolved over 10+ months of intensive daily use
Comprehensive SEO analysis plugin for Claude Code. 25 sub-skills (21 core + 1 orchestrator + 1 framework + 2 extension mirrors) and 18 sub-agents cover technical SEO, content quality, schema, sitemaps, Core Web Vitals, local SEO, backlinks, AI/GEO, ecommerce, hreflang, SXO, clustering, drift monitoring, and Google APIs. Includes optional MCP extensions, SPA-aware rendering, portability, and hardened SSRF/DNS-rebinding safe fetchers.