adeonir
- 19 skills
- 0 followers
- 6 hours ago last updated
- ▌
- ▌ Frontend Design · adeonirCreate distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
- ▌ Notes · adeonir bundleObsidian note creation and updates for projects, challenges, achievements, transcriptions, companies, and job applications. Use when documenting work or preserving meeting and lecture notes. Not for session handoffs or repository-wide project context.
- ▌ Handoff · adeonir bundleConversation handoff scoped to the current project, for resuming work across sessions. Use when checkpointing, ending a session, loading prior context, or clearing a handoff. Not for handoffs between projects, durable session notes, or repository-wide project context.
- ▌ Wrap Up · adeonir bundleEnd-of-session context persistence to Obsidian. Use when closing a session, saving work, or documenting what was accomplished. Not for mid-session notes, conversation handoffs, or repository-wide project context.
- ▌ Craft UI · adeonir bundleCreates lo-fi wireframes for UI structure and hi-fi mockups for visual directions. Use for landing pages, dashboards, product UI, and app screens. Not for visual identity, copywriting, single-component design, built-UI audits, or code review.
- ▌ Anti Slop · adeonir bundleProse editing that removes AI-writing patterns while preserving facts, voice, and format. Use when humanizing or checking a draft for machine-written patterns. Not for authorship detection, source-code changes, fact-checking, translation, or product-copy authoring.
- ▌ Brainstorm · adeonir bundleIdea exploration from a blank problem space or stress-testing an existing plan before building. Use when comparing approaches, finding gaps, reconsidering a direction, or weighing a pivot. Not for documenting a finalized direction.
- ▌ Copywriting · adeonir bundleCreates and evaluates copy for brand, editorial, product, UX, conversion, and informational surfaces. Use when writing, extracting, editing, syncing, critiquing, or auditing copy. Not for visual identity, page layout, or standalone social bios.
- ▌ Docs Writer · adeonir bundleProduct and technical document creation through guided discovery, including PRDs, positioning docs, Design Docs, and ADRs. Use when defining requirements, strategy, trade-offs, or architecture decisions. Not for UI design, implementation specs, or meeting notes.
- ▌ Design Brief · adeonir bundleVisual identity development and validation through the official `DESIGN.md` schema and CLI. Use when creating, refreshing, syncing, previewing, exporting, or diffing design tokens. Not for page layout, rendered variants, product copy, feature specs, production code, or code review.
- ▌ Epic Tracker · adeonir bundleRoadmap and delivery artifact management in Linear or GitHub. Use when creating, editing, decomposing, moving, or updating roadmaps, epics, stories, bugs, or tasks. Not for implementing a named story, feature status in a spec, project overviews, or quick fixes.
- ▌ Debug Tools · adeonir bundleEvidence-led debugging for unexpected, silent, or intermittent failures. Use when tracing bugs, adding targeted logs, or verifying fixes. Not for known one-line fixes, runtime review of deployed services, or PM bug triage.
- ▌ Git Helpers · adeonir bundleGit workflow for conventional commits, pull request creation, and pull request merging. Use when committing, opening or pushing a pull request, or merging one. Not for code review, acceptance-criteria checks, general branch management, or session wrap-up.
- ▌ Review Lens · adeonir bundleCode review in quick and deep modes, with confidence-scored findings. Use for diff review, guideline audits, re-reviewing fixes, or applying findings before a pull request. Not for markdown or prose review, acceptance-criteria verification, visual design review, or commit and branch mechanics.
- ▌ Spec Driven · adeonir bundleSpec-driven feature work with traceable requirements, design, tasks, audit, and validation. Use when planning, designing, implementing, or validating a feature. Not for unknown-bug diagnosis, standalone product or technical documents, PR or commit mechanics, or backlog tracking.
- ▌ Plain Spoken · adeonir bundleClear, precise technical prose that preserves facts, requirements, and terms. Use for explanations, procedures, specifications, documentation, incident reports, and brief factual answers. Not for code-only output, raw logs, compliance certification, or marketing copy.
- ▌ Rule Creator · adeonir bundleClaude Code rule management at project and user level. Use when defining conventions, scoping, listing, editing, extracting, or deleting rules. Not for procedural workflows, lifecycle hooks, or one-off task instructions.
- ▌ Skill Reliability · adeonir bundleAnalyzes a skill's end-to-end reliability — trigger precision plus compound workflow risk (step count, step nature, variance hotspots) — and proposes verifiable fixes it can apply on confirmation. Use when evaluating a skill's hit rate, checking whether a description fires on the right requests, finding prompt-driven or generation steps that drag reliability, or deciding where scripts, idempotence, or explicit inputs/outputs help most. Invoke as /skill-reliability with a skill name, or when the user asks about steps vs reliability, hit rate, trigger precision, or confiabilidade of a specific skill.