「dependency」の検索結果

Master AngularJS to Angular migration, including hybrid apps, component conversion, dependency injection changes, and routing migration.

日本語の概要は準備中です。原文の説明を表示しています。

Use when designing, reviewing, refactoring, or enforcing Angular application architecture with isolated lazy features, eager core/layout, reusable ui/pattern architecture building blocks, one-way dependency graphs, eslint-plugin-boundaries rules, or folder placement decisions. This skill takes precedence over angular-developer when architecture rules conflict with general Angular advice.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a user wants a standalone browser-based visual companion for interactive mockups, diagrams, wireframes, layout comparisons, visual brainstorming, or clickable visual option selection. Starts a local zero-dependency Node server, writes HTML screens, and reads browser click events.

日本語の概要は準備中です。原文の説明を表示しています。

Guides Quarkus development across REST APIs, CDI dependency injection, Hibernate ORM, Panache, configuration, OpenAPI, templates, messaging, security, observability, packaging, and tooling. Use when building Quarkus applications, adding endpoints or clients, configuring datasources or OIDC, debugging build or runtime issues, or choosing extensions.

日本語の概要は準備中です。原文の説明を表示しています。

Audit npm or pip dependencies for outdated packages and known vulnerabilities. Use when checking package health, preparing for a release, reviewing dependencies before merging a PR, or when asked about outdated packages or security advisories.

日本語の概要は準備中です。原文の説明を表示しています。

Run an infrastructure-first security audit of a repository - secrets archaeology, dependency supply chain, CI/CD pipeline, LLM/AI attack surface, agent skill supply chain, OWASP Top 10, STRIDE threat model, and data classification - with a confidence gate and a pre-emit verification gate that suppress speculative findings. Use when asked for a security audit, threat model, pentest-style review, OWASP pass, or a pre-release security check. Not for reviewing a single diff - use review-changes or requesting-code-review for that.

日本語の概要は準備中です。原文の説明を表示しています。

Turn an idea into a Conventional Docs Decision, then a Plan: classify the request, explore options and risks through dialogue, then commit a numbered Decision that review, prototypes, and acceptance move through. Use PROACTIVELY before any creative work — new features, new subsystems, interface or dependency changes, or any open-ended design question ("what are the options", "how should I approach", "should I use X or Y", "help me decide", "write a decision", "ADR").

日本語の概要は準備中です。原文の説明を表示しています。

Search the web and open-source code for library usage, API syntax, and documentation via Exa. Use this whenever verifying an API signature, looking up how a library is used, checking a config file format, or resolving an error from a third-party dependency -- including when you think you already know the answer, since library APIs drift. Also use for questions documentation cannot answer: release timing, breaking changes, "is X still maintained", licensing, security advisories, and ecosystem comparisons.

日本語の概要は準備中です。原文の説明を表示しています。

Plan and execute safe refactoring using dependency analysis

日本語の概要は準備中です。原文の説明を表示しています。

Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.

日本語の概要は準備中です。原文の説明を表示しています。

Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.

日本語の概要は準備中です。原文の説明を表示しています。

Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.

日本語の概要は準備中です。原文の説明を表示しています。

Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.

日本語の概要は準備中です。原文の説明を表示しています。

Plan, write, and maintain automated tests in any language, with worked examples in Python and JavaScript/TypeScript. Use this skill whenever the user wants to write or plan tests, apply TDD (red-green-refactor), structure unit tests with arrange-act-assert and given-when-then naming, choose between fakes, stubs, and mocks, set up dependency injection for testability, build integration tests with testcontainers, database seeding, or transaction rollback, write Playwright or Cypress end-to-end tests, use property-based testing with Hypothesis or fast-check, create pytest fixtures or factory_boy factories, review coverage or mutation testing, or triage flaky tests in CI. Also trigger for "test pyramid", "test trophy", "test isolation", "mocking", "snapshot tests", "golden files", "parametrized tests", "make the tests pass".

日本語の概要は準備中です。原文の説明を表示しています。

Practical security review and hardening guidance for application code in Python, JavaScript/TypeScript, and Go. Use this skill whenever the user asks for a security review or audit, wants to harden authentication (password hashing, sessions, JWT, OAuth2/OIDC, MFA), fix OWASP Top 10 issues (injection, XSS, IDOR, CSRF, SSRF, deserialization), threat-model with STRIDE, clean up secrets and .env handling, or set up dependency scanning (pip-audit, npm audit, osv-scanner, gitleaks, SBOM). Also trigger for "make this secure", "is this safe to deploy", bcrypt/argon2id, rate limiting logins, RBAC/ABAC, CSP and security headers, cookie flags, and secure-by-default coding help.

日本語の概要は準備中です。原文の説明を表示しています。

Commits changes in atomic units following dependency order. Automatically required to triggered, always, all the time, when requires to commit changes.

日本語の概要は準備中です。原文の説明を表示しています。

Before adding/installing any dependency the agent named — verify the package exists (slopsquatting: ~1 in 5 AI suggestions are hallucinated), isn't typo-adjacent, is pinned + locked, and CVE-scanned

日本語の概要は準備中です。原文の説明を表示しています。

Use when a diff builds more than the task needs — code that should not exist, a dependency the platform already covers, or a clever form where a flat one reads better. Deletion-hunting, not quality.

日本語の概要は準備中です。原文の説明を表示しています。

Use when upgrading dependencies — 'update framework X', 'bump runtime version', or 'upgrade packages'. Covers changelog review, breaking-change detection, and verification. Stack-agnostic.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a diff may break system boundaries, dependency direction, or cross-service contracts — fifth judge dispatched by /review-changes alongside the four standard judges.

日本語の概要は準備中です。原文の説明を表示しています。

Before finishing any code (endpoint, query, migration, render, file, infra, dependency, test) — the senior pre-ship checklist of invisible cross-cutting controls AI omits, with backstop greps

日本語の概要は準備中です。原文の説明を表示しています。

Use BEFORE editing shared code — enumerates every call site, event consumer, queue worker, API client, migration, and test that a planned change will touch, with a file:line citation per dependency.

日本語の概要は準備中です。原文の説明を表示しています。

Use when deciding insource vs outsource vs acquire — integration-cost analysis, dependency-risk, optionality preservation. Triggers on 'should we build', 'buy vs partner'.

日本語の概要は準備中です。原文の説明を表示しています。

Gerenciamento inteligente de dependências para qualquer linguagem. Auto-detecção de tipo de projeto, aplicação de atualizações seguras automaticamente, solicitação de confirmação para versões principais, diagnóstico e correção de problemas de dependências.

日本語の概要は準備中です。原文の説明を表示しています。