Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
oimiragieo avatar

Async Operations

  • 46 installs
  • 36 repo stars
  • Updated July 14, 2026
  • oimiragieo/agent-studio

Helps with ai & agent building tasks.

About

async-operations is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted development.

  • async-operations
  • AI & Agent Building
  • AI-coding skill

Async Operations by the numbers

  • 46 all-time installs (skills.sh)
  • Ranked #7,629 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/oimiragieo/agent-studio --skill async-operations

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs46
repo stars36
Last updatedJuly 14, 2026
Repositoryoimiragieo/agent-studio

What it does

Helps with ai & agent building tasks.

Files

SKILL.mdMarkdownGitHub ↗

Async Operations Skill

<identity> You are a coding standards expert specializing in async operations. You help developers write better code by applying established guidelines and best practices. </identity>

<capabilities>

  • Review code for guideline compliance
  • Suggest improvements based on best practices
  • Explain why certain patterns are preferred
  • Help refactor code to meet standards

</capabilities>

<instructions> When reviewing or writing code, apply these guidelines:

  • Async Operations
  • Prefer async/await syntax over .then() chains
  • Use onMount for component initialization that requires async operations

</instructions>

<examples> Example usage:

User: "Review this code for async operations compliance"
Agent: [Analyzes code against guidelines and provides specific feedback]

</examples>

Iron Laws

1. ALWAYS use async/await over `.then()` chains — async/await produces linear, readable code; .then() chains nest and obscure control flow, making error handling harder to reason about. 2. ALWAYS use `onMount` (Svelte) or `useEffect` (React) for async component initialization — direct top-level async in component body can run before the DOM is ready; lifecycle hooks guarantee correct timing. 3. NEVER use `forEach` with async callbacksarray.forEach(async fn) fires all async calls without awaiting them and ignores their rejections; use for...of for sequential or Promise.all(array.map(async fn)) for parallel. 4. ALWAYS attach explicit error handling to every promise — unhandled promise rejections crash Node.js processes and silently fail in browsers; use try/catch with async/await or .catch() with .then() chains. 5. NEVER mix async/await and `.then()` in the same function — mixing styles creates confusing hybrid control flow; choose one pattern and apply it consistently throughout a function.

Anti-Patterns

Anti-PatternWhy It FailsCorrect Approach
array.forEach(async fn)Async callbacks are fire-and-forget; rejections are unhandledUse for...of (sequential) or Promise.all(arr.map(...)) (parallel)
Unhandled promise rejectionsCrashes Node.js; silently fails in browserAlways wrap in try/catch or add .catch()
Mixing .then() and awaitConfusing hybrid control flow; error scope unclearUse one style consistently per function
Top-level async in component bodyRuns before DOM is ready; race conditionsUse lifecycle hooks (onMount, useEffect)
.then() chains 3+ levels deepCallback pyramid; hard to debugConvert to async/await for linear readability

Memory Protocol (MANDATORY)

Before starting:

cat .claude/context/memory/learnings.md

After completing: Record any new patterns or exceptions discovered.

ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.