Tensology.com

Operate as an agentic engineer using eval-first execution, decomposition, and cost-aware model routing.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build persistent multi-agent operating systems on Claude Code. Covers kernel architecture, specialist agents, slash commands, file-based memory, scheduled automation, and state management without external databases.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Configures health check endpoints for Kubernetes readiness/liveness/startup

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Reduces JS/TS bundle size via unused deps, tree-shaking, code splitting with keep/discard

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Regression check — diff a live page's web accessibility (a11y) violations against a baseline. By default it compares your uncommitted changes (stash-based); pass `--branch [<name>]` to compare against a branch. Reports the new WCAG violations introduced, the ones fixed, and the count of pre-existing ones. Use it for 'did my change break accessibility', 'what a11y issues did this PR add', or as a CI gate. For a full scan of one page use `accessibility-scan`; for a whole site use `accessibility-audit`.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert UI/UX design guidance for unique, accessible interfaces. Use for visual decisions, colors, typography, layouts. Always ask before making design decisions. Use this skill when the user asks to build web components, pages, or applications.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build an animation from scratch, making the decisions in the order that determines whether it feels right — should it animate at all, what purpose, which tool, which properties, which curve and duration, how it interrupts, how it exits. Writes the implementation. Use when asked to animate something, add motion, make a component feel alive, or build a transition. For critiquing existing motion use review-animations; for auditing a whole codebase use improve-animations.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

One page, automated tier — run the web accessibility (a11y) rule engine against a live page and locate every violation it can detect mechanically. Pass a URL, a config target name (e.g. `accesslint:accessibility-scan dev`), or nothing to use the default target from `accesslint.config.json`. Ensures a debuggable Chrome, runs the @accesslint/core engine over CDP, and returns a worklist of live-DOM WCAG 2.2 violations, each grounded to its DOM selector and source `file:line`. Locates; doesn't edit. Use it for 'is this page accessible', 'check a11y on this URL', 'find contrast and alt-text issues', or to verify a UI change. For hands-on keyboard and screen-reader checks use `accessibility-inspect`; for a whole site or product use `accessibility-audit`; to diff against uncommitted changes or a branch use `accessibility-diff`.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Configures CORS policy for development and production

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

One page, hands-on manual tier — drive a live page through the web accessibility (a11y) checks a rule engine can't decide: keyboard operation and focus order, screen-reader names, roles and states from the accessibility tree, reflow and zoom, reduced motion, form errors, and target size. Grades each finding by evidence basis (verified / confirm-with-a-human / human-required) and severity, and closes every criterion in a ledger: verified, flagged, not exercised, or N/A. Locates and assesses; does not fix (use `accessibility-fix`). Use it for keyboard testing, focus-order checks, screen-reader or a11y-tree review, reflow and zoom at 200%, or 'is this operable, not just lint-clean'. The automated tier is `accessibility-scan`; `accessibility-audit` runs both across a sampled site.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Whole site or product — a full web accessibility (a11y) audit against WCAG 2.2, following the WCAG-EM methodology. Defines scope, samples representative pages and flows, runs the automated tier (`accessibility-scan`) and the hands-on manual tier (`accessibility-inspect`), and produces one conformance report. Grades each finding by severity and evidence basis, and states per-criterion conformance as pass, fail, or undetermined (needs a human). Use it for 'audit my site for accessibility', 'is this product accessible', 'a11y audit', 'WCAG or Section 508 conformance report', or any multi-page assessment. Assesses; does not fix (use `accessibility-fix`) or diff (use `accessibility-diff`). For a single page use `accessibility-scan`; for hands-on keyboard and screen-reader checks use `accessibility-inspect`.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when Codex is running work that originated from DecisionsAI tickets, projects, workflows, or Initiative proposals.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Competitive benchmarks, solution research, and hypothesis generation for identified bottlenecks

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Configures global exception handling middleware

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Runtime profiling with multi-metric measurement, instrumentation, and performance map generation

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Multi-cycle diagnostic pipeline: profile → research → optimize → repeat with full-stack bottleneck analysis

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Multi-file hypothesis testing with keep/discard loop, compound baselines, and experiment logging

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Upgrades npm/yarn/pnpm dependencies with breaking change handling

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Upgrades Python pip/poetry/pipenv dependencies with breaking change handling

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when you have a spec or requirements for a multi-step task, before touching code

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when creating new skills, editing existing skills, or verifying skills work before deployment

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'how do I show up in AI answers,' 'LLM mentions,' 'optimize for Claude/Gemini,' 'llms.txt,' 'OKF,' 'Open Knowledge Format,' 'knowledge bundle,' or 'agent-readable site.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see schema.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.