795건 · 관련도순
Develop Angular v20+ applications using Signals for reactive state and Standalone Components. Supports gradual migration from NgModules, Zoneless configuration, server-side rendering, hydration, and performance optimization with development testing before production use.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Helps build Angular v20+ applications with Signals, which track changing values, and self-contained Standalone Components. Covers state management, server rendering, performance improvements, and testing, including gradual updates to existing applications.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Retrieve individual buy and sell signals from tracked investor wallets on BSC and Solana. Compare prices at detection with current prices, review maximum gains and exit rates, and check whether signals remain active.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Plan how an Angular app stores and updates data used by its screens. Covers local and shared state, choices involving Signals, NgRx, and RxJS, synchronization with server data, debugging, and migration from older patterns.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
When the user wants to improve E-E-A-T, add trust signals, or optimize for expertise and authority. Also use when the user mentions "E-E-A-T," "E-E-A-T signals," "experience expertise authority trust," "author bio," "YMYL," "trust signals," "expertise signals," "authority signals," "citations," "references," or "credibility." For headings, use heading-structure.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build Table v9 tables in Angular using injectTable and FlexRender. Guidance covers signal-driven data updates, reusable table components, and connections to TanStack Query for data fetching and TanStack Virtual for displaying large tables.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Detect buying signals across TAM companies and watchlist personas. Three-phase architecture: (1) free diff-based signals from existing data (headcount growth, tech stack changes, funding rounds), (2) Apify-powered signals (job postings, LinkedIn content analysis, profile changes), and (3) post-processing with dedup, scoring, and lead status updates. Writes signals to Supabase signals table for downstream activation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Set up signal capture for a Simulink Real-Time application using `slrealtime.Instrument`. Use when choosing which signals a real-time application captures and where the data goes — test-pointing or canvas-badging a signal before build (`TestPoint`, `DataLogging`), constructing an Instrument from an `.mldatx`, calling `addSignal`, `addInstrumentedSignals`, `addFileLogSignals`, `validate`, `connectCallback`, `copy`, or `generateScript`, attaching an instrument to `tg.Instruments` via `addForFileLog`, `addForSDI`, or `addForMATLAB`, setting up live-streaming signals, dynamic file-log workflows, or persisting an instrument as M-code. Selects and routes signals only — not for configuring, building, running, or connecting applications onto targets.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Deprecated alias. This skill was renamed to `deepline-scoring`. Use when a user or script still invokes `/niche-signal-discovery`: immediately load and follow the `deepline-scoring` skill instead. Triggers: ICP analysis, niche signals, won vs lost analysis, differential signals, signal discovery, ICP signal report, account scoring signals, lead scoring, first-party signals, buyer signals.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when searching for buying signals, detecting intent data, scoring prospect readiness, or monitoring accounts for trigger events. Triggers: 'scan for signals', 'find buying signals', 'who is ready to buy', 'intent signals', 'signal scoring', 'account signals'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
State management for Angular 18-21: signals (signal/computed/effect), services-as-state, NgRx Store + Effects + Selectors, NgRx Component Store, NgRx Signals (newer signal-based store). RxJS essentials — operators, async pipe, takeUntilDestroyed, signal/observable interop. Use this skill to: - Pick the right state tool (signals / services / NgRx variant / vue-query equivalent). - Use signals correctly (signal/computed/effect — when each). - Build a Pinia-style service-as-state singleton. - Set up NgRx Store + Effects + Selectors. - Use RxJS without leaking subscriptions (async pipe, takeUntilDestroyed, Subject patterns). - Bridge signals ↔ observables via toSignal / toObservable. Do NOT use this skill for: - General Angular conventions (see angular-conventions). - Routing state (see angular-routing). - Form state (see angular-forms). - Testing state (see angular-testing).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Work on advanced RuView sensing with signals from multiple WiFi nodes. Explore position estimation, three-dimensional occupancy reconstruction, changes in movement patterns over time, and defenses against suspicious signals, with guidance on implementation modules and validation.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Generate trading signals using Smart Money Concepts, a framework for interpreting institutional trading behavior. Analyze trend continuation, reversals, price gaps, and order concentration zones, then combine structural signals and gaps to determine a trading direction.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Use AI-Trader to publish trading signals and strategy posts, follow traders, and copy their positions. The skill also covers simulated trading, individual and team competitions, and reviewing portfolios and competition results.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build Angular 17+ applications with standalone components, routing, and shared application state. Covers reactive data handling with RxJS, performance improvements, and unit and integration tests, with code and explanations of architecture choices.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build event-driven, decoupled Godot 4.7 gameplay with signals and node groups: declare and emit custom signals, connect with Callables (incl. bind/one-shot), and broadcast to many nodes via groups and call_group. Use when wiring node communication in a Godot project, replacing tight references with signals, emitting/connecting events, or porting 3.x connect("sig", self, "method") code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Angular is opinionated and comprehensive - it gives you everything: routing, forms, HTTP, dependency injection, testing. The learning curve is steep, but once you're in, you move fast. The structure it enforces is why enterprises love it. This skill covers Angular 17+, standalone components, signals, the new control flow syntax, and modern Angular patterns. Key insight: Angular's power is in its DI system and RxJS integration. Master those, and everything else follows. 2025 lesson: Standalone components are the future. NgModules aren't going away, but new projects should start standalone. Signals are Angular's answer to fine-grained reactivity - learn them. Use when "angular, angular component, angular service, angular routing, angular forms, rxjs, ngrx, angular signals, standalone component, angular ssr, angular, typescript, frontend, spa, enterprise, rxjs, signals, standalone" mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Checkable-ish surface presentation signals a reviewer notices first — duplicate/near-identical tables, leftover pipeline/template strings, too-few or LLM-looking figures, and page-padding. AUXILIARY ONLY and weak by design: a deterministic pass (tools/check_presentation.py — dup-table + pipeline-artifact) plus a fresh cross-model GROSS-cases-only semantic pass (thin-float, LLM-figure, page-padding), every above-info finding span-anchored to the evidence ledger (claims.json). The adjudicator CAPS everything at minor (SURFACE_ONLY_SKILLS + SURFACE_PATTERNS) — these contribute at most SOFT_FLAGS, never a HARD verdict — default false_positive_risk:high. NOTE: the pure AI writing-STYLE impressions (AI-flavor prose, defensive 'not-X-but-Y' hedging, narrative-arc, jargon-stuffing, invented codenames) MOVED to the zero-verdict-weight AIS track — for those use skills/ai-style-impressions, NOT this. Emits presentation-signals.findings.json; NEVER computes the verdict. Triggers: "presentation signals", "surface check", "duplicate tables", "排版信号".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Signal-based prospecting — read target companies' public websites for buying signals (ads running, incumbent agency, tech stack, hiring, stale content, missing booking) with evidence URLs, then build a cohort you can explain. Use when asked to "find buying signals", "profile these companies", "which accounts should we target", "build a target list from these domains", or "what changed at these accounts".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Focused Signals scout for PostHog projects running Replay Vision scanners — the standing LLM probes that watch session recordings and write `$recording_observed` events. Watches two promises: that enabled scanners are actually observing (throughput / success-rate cliffs, exhausted quota — a silent watch gap), and that what the scanners see in aggregate gets surfaced (a monitor's `yes`-rate or a scorer's score stepping away from its own baseline, a classifier tag or a recurring summarizer theme concentrating across many sessions). It is the agentic pull complement to the per-session push path: scanners with `emits_signals` already emit one signal per session into this same inbox, so this scout never repeats them — it adds the cross-session shape the per-session probe can't see. Emits findings only when they clear the confidence bar; otherwise writes durable memory and closes out empty. Self-contained peer in the signals-scout-* fleet.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
General Signals scout for PostHog projects. Cross-product explorer that scans a team's project and emits findings into the Signals inbox. Sibling signals-scout-* specialists each watch a single product surface in depth; this scout looks for cross-product correlations and explores the surfaces no specialist covers. Each scout runs on its own schedule (default hourly), so general fires independently of the specialists over time.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
How to explore and make sense of PostHog Signals scouts — the scheduled agents that scan a project and emit findings into the Signals inbox. Use when a user wants to understand what scouts they have, how each one is behaving, and whether the fleet is actually working. Covers surveying the fleet and its schedules, reading recent scout runs and drilling into a single run's reasoning, inspecting the durable scratchpad memory the fleet has built up, tracing a run to the findings it emitted, and assessing a scout's health and performance over time (cadence, success rate, emit rate, signal-to-noise). Read-only and exploratory — to write or tune a scout, use `authoring-signals-scouts` instead. Trigger on "what are my scouts doing", "how is my <x> scout performing", "show me recent scout runs", "why did this scout find/emit nothing", "what has the fleet learned", "explore scout run <id>", "is my scout working".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
How to author, edit, and adapt PostHog Signals scouts — the scheduled agents that scan a project and emit findings into the Signals inbox. Use when a user wants to customize a canonical scout for their own setup (narrow its scope, retune its thresholds, add disqualifiers), tweak a scout's schedule or dry-run posture, or write a brand-new scout from scratch for a specific use case (a custom event, a product surface no canonical scout covers). Covers the scout SKILL.md anatomy, the emit contract, the dedupe + scratchpad-memory conventions, the per-team skills-store path vs the canonical in-repo path, and the emit-and-inspect test loop (with dry-run as an optional safety net). Trigger on "write/edit/customize a signals scout", "new scout for X", "tune my scout schedule", "make a scout that watches <event>".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Angular 화면과 서비스를 만들고 상태 관리, 폼, 화면 이동을 설계합니다. 프로젝트 버전에 맞는 구현 방식을 선택하고 테스트 작성과 빌드 확인을 지원합니다.