aboudjem
- 26 skills
- 0 followers
- 10 hours ago last updated
- ▌ AWS Cost Audit · aboudjem bundleUse when a user wants to audit, understand, reduce, or optimize their AWS bill or cloud costs, finding idle, unused, or orphaned resources, rightsizing over-provisioned compute, checking Savings Plans / Reserved Instance coverage, NAT gateway and data-transfer costs, S3 storage and lifecycle, CloudWatch log retention, untagged or unexplained spend, per-resource cost attribution ("what is this costing me and why"), or building a savings plan or cost dashboard. Triggers include "AWS bill too high", "cut/lower AWS costs", "FinOps", "Cost Explorer", "where is my money going", "unused AWS resources", and "cloud cost audit".
- ▌ Loopify · aboudjem bundleHand Claude a job that repeats. Come back to a log of what every tick did, not a loop you have to babysit. loopify writes the brief (a standing file the loop re-reads every tick) and the line (one short `/loop` string you paste into Claude Code's built-in `/loop`), with a stop rule, a tick cap and safety rails built in. Use when the user says "loopify", "loopify this", "loopify <job>", "/loopify <job>", "prep a loop", "make a brief for /loop", "set up a recurring job", "keep X healthy every N minutes", "babysit", "poll", or "check … on a schedule". For a job that FINISHES — one big task with a definition of done — use goalify and /goal instead; loopify is for a job that repeats. This skill AUTHORS the two artifacts now; it does NOT start the loop. For work to be done right now in this session use autopilot, ultrawork, or ralph, not loopify.
- ▌ Solidity Style Guide · aboudjem bundleApply the Aboudjem/solidity-style-guide rules to Solidity code — review, rewrite, or audit for naming, layout, formatting, NatSpec, custom errors, ERC-7201 storage, gas patterns, and Foundry test structure. Trigger when the user asks to "review Solidity style", "apply the style guide", "format .sol file", or mentions Solhint / Prettier / Foundry conventions in a Solidity repo.
- ▌ Sniff · aboudjemUse when the user types /sniff, or asks to "scan this project for bugs", "find bugs in my app", "QA my site", or "walk my app and tell me what's broken". For a running web app, finds real, reproducible issues (broken pages/links, console & network errors, broken forms, empty/placeholder data, state-loss, bad loading/error states, responsive and accessibility problems), each with reproduction proof, severity, confidence, and a fix. No API key needed.
- ▌ Sniff Fix · aboudjemScan the project and auto-fix safe issues (remove debugger statements, console.log calls, and other auto-fixable problems).
- ▌
- ▌ Recap Setup · aboudjemUse when the user types /recap setup, /recap config, or asks Recap Studio to "configure", "initialize", or "set defaults". Writes recap-studio.config.ts with safe defaults and validates env.
- ▌ Recap Topic · aboudjemUse when the user types /recap, /recap topic, /recap "<subject>", or asks Recap Studio to "make a one-page explainer", "summarize a topic", or "build a visual page about X". Routes to /recap session when the input is "session", "repo", or empty inside a git repo with uncommitted changes.
- ▌ Recap Session · aboudjemUse when the user types /recap session, /recap repo, /recap session --deep, or asks Recap Studio to "explain my coding session", "summarize this branch", "wrap up what we built", or "explain what changed". Produces a one-page page that explains a large coding session or repository change to a smart beginner in under 5 minutes.
- ▌ Recap Validate · aboudjemUse when the user types /recap validate, asks Recap Studio to "score the page", "run validation", "qa the recap", or wants the multi-agent quality report regenerated. Dispatches the validation board and writes a structured report.
- ▌ A11Y Audit · aboudjemAccessibility audit covering WCAG 2.2, contrast, focus, keyboard, screen reader, and touch targets. Use when the user asks for an accessibility audit, an a11y review, a WCAG check, an accessibility check, or an a11y audit.
- ▌ Flow Audit · aboudjemUser flow and navigation audit covering information architecture, onboarding, and error states. Use when the user asks for a flow audit, a navigation audit, an onboarding review, or help with a UX flow.
- ▌ Type Audit · aboudjemTypography-only audit covering font selection, type scale, readability, hierarchy, and performance. Use when the user asks to audit typography, run a typography or type audit, review fonts, fix their fonts, or work on the type system.
- ▌ Color Audit · aboudjemColor-only audit that extracts, evaluates, and recommends improvements for the project's color system. Use when the user asks to audit colors, run a color review or color audit, fix their colors, or work on the color palette or color system.
- ▌ Design Audit · aboudjemFull project design audit that orchestrates all agents, scores across 12 dimensions, and generates a prioritized action plan. Use when the user asks to audit their design, run a design review or UX audit, review their UI, or asks how their design looks.
- ▌ Design Score · aboudjemQuick design score card covering 12 dimensions with the top 5 improvements, in under 2 minutes. Use when the user asks for a design score, to score their design, to rate their UI, or for a quick audit.
- ▌ Layout Audit · aboudjemLayout and spacing audit covering grid, spacing consistency, density, and responsive behavior. Use when the user asks to audit the layout, run a layout audit or grid audit, review spacing, or fix their spacing.
- ▌ Design Tokens · aboudjemGenerate or improve a complete design token system covering color, typography, spacing, radius, shadows, and motion. Use when the user asks for design tokens, to generate tokens, or to build a token system.
- ▌ Refactor Plan · aboudjemPrioritized redesign action plan covering quick wins, medium effort, and major rework. Use when the user asks for a refactor plan, a redesign plan, an improvement plan, or what they should fix first.
- ▌ Theme Builder · aboudjemBuild a light/dark theme from scratch or improve an existing one, with a complete surface, text, and interactive color system. Use when the user asks to build or create a theme, use the theme builder, or set up a light and dark theme.
- ▌ Design Compare · aboudjemCompare the current design against a reference product or competitor. Use when the user asks to compare designs, run a design compare, or benchmark against another product.
- ▌ Component Audit · aboudjemComponent consistency audit covering state coverage, hierarchy, and patterns. Use when the user asks for a component audit, a component review, or a check of UI consistency.
- ▌ Style Direction · aboudjemVisual style direction recommendation with current style analysis plus the top 3 directions and implementation guidance. Use when the user asks for a style direction, a visual or design direction, or what style they should use.
- ▌ Design Checklist · aboudjemInteractive pre-launch design quality checklist. Use when the user asks for a design checklist, a launch checklist, or a pre-launch design pass.
- ▌ Goalify · aboudjem bundleHand Claude a huge task. Come back to proof it's done — not a promise that it is. goalify writes the brief (a file with the instructions the run works from) and the condition (a short string you paste into `/goal`), because `/goal` takes a condition string, never a file path. Use when the user says "goalify", "goalify this", "goalify <task>", "/goalify <task>", "prep a goal", "prepare a brief for /goal", "make an md for /goal", "set up an autonomous run to launch later", or wants a Codex `/goal` objective. This skill AUTHORS those two artifacts now; it does NOT execute the work in this session. For a task to be done immediately here, use autopilot, ultrawork, or ralph instead, not goalify.
- ▌ Humanizer 3 · aboudjem bundleDetects 53 AI writing patterns and rewrites text in five voice profiles so it reads like a specific human wrote it, with an optional 0-100 AI-tell score. Use when text sounds AI-generated or like a chatbot, when preparing a blog post, README, or LinkedIn post for publication, when auditing prose for AI tells, or when editing a Markdown file in place. Triggers on phrases like "humanize this", "make this sound less AI", "make this sound human", "remove AI tells", "does this read like ChatGPT", and "rewrite so it does not sound AI-generated". Pure Markdown, zero dependencies, no network calls.