Total 58,638 skills
Showing 12 of 58638 skills
Use when the user wants to step through a feature's checkpoints chronologically, pausing at each step to ask questions. Triggers on phrases like "replay <feature>", "walk me through how X was built", "show me the journey of", "step me through how Y was implemented", and "replay the last week"
Use when an agent session ran outside the repo whose commits should record it — e.g. launched from a higher-level folder, a non-Entire repo, or one repo but editing another — to attach the session to each affected Entire-enabled repo's HEAD commit.
Svelte template directives ({@attach}, {@html}, {@render}, {@const}, {@debug}). Use for DOM manipulation, third-party libs, tooltips, canvas, dynamic HTML. @attach replaces use: actions.
Identify underserved market gaps and unmet customer needs in e-commerce. Analyzes competitor blind spots, review pain points, search demand without adequate supply, and emerging customer segments.
Performs a meta-level review of how well an implementation followed its plan, classifying divergences and recommending AI-Layer improvements. Use after an execution report exists to find bugs in the process, not the code.
As a standard S0 pre-skill for larger page workflows like `hiui-page-workflow`, it focuses on requirement refinement for B-end back-office systems and before HiUI page generation. It transforms vague or abstract back-office/management/operation/configuration/approval workflow requirements into executable product solutions, MVP scopes, user flows, business rules, traceable page inventories, product PRDs, global generation contexts, page-level prompts, and HiUI handoff packages. It is suitable for clarifying back-office product ideas, converting rough requirements into PRDs or product solutions, breaking down work surfaces such as lists/details/editing/configuration, defining role permissions/data permissions/state machines/audit rules, and supplementing permission matrices, state transition tables, field dictionaries, exception and audit matrices, batch/import-export specifications, and legacy system transformation and release strategies when needed; it also acts as a B-end product expert to provide judgments including business value decomposition, priority suggestions, solution trade-offs, multi-tenant/version/activation models, master data and system boundaries, anti-pattern identification and risk prompts, continuously turning vague B-end requirements into implementable inputs; when requirements arise in existing projects/repositories, it is also used to perform context-aware requirement refinement combining the current repository's pages, modules, interfaces, types, and documents.
Manually-invoked skill that stops overthinking and forces a short, practical decision. Use only when the user explicitly invokes stop-overthinking.
Answer market-intelligence questions about pay, demand, and trends by querying the SOLID.Jobs live market-statistics API — choosing contextually between a current-snapshot scope query and a multi-year role trend report. Use when the user asks "what's the market like for X", "how does X pay", "is X in demand", "has X's pay changed over the years", or wants a salary/trend report for a role, category, or city.
Search SOLID.Jobs offers from a natural-language request. Translates phrases like "senior Go, remote, 25k+ in Warsaw" into sjctl search flags, runs the query, and presents the best matches. Use when the user wants to find or browse job offers.
Detect, review, and fix code-quality and correctness issues in an AEM as a Cloud Service project — locally, with no external services or network calls. Use whenever a user wants to check, review, assess, audit, scan, modernize, upgrade, or fix AEM Java, Sling Models, OSGi, or Maven code — for example: "check my Sling Models are implemented correctly", "review my @Inject usage", "are my Maven dependencies up to date", "scan this AEM project for issues", "modernize my Sling Models", or "fix code-quality problems". Name the files to assess, or ask it to scan the repo; it detects issues, plans, and — only when you ask — applies surgical edits on a branch or in place, then verifies with mvn compile. It recognises the intent and handles each issue type itself, reporting anything it cannot yet fix.
Crawl and validate all internal and external links across an AEM Edge Delivery Services site. Uses the query index or sitemap to discover pages, extracts links from .plain.html renditions, checks HTTP status codes, and produces a prioritized report of broken, redirecting, and insecure links. Use when auditing link health before launch, after a migration, or as a periodic maintenance check.
Reconcile a converted/built web page against its source prototype with two complementary probes — a PIXEL/layout diff (stretched images, dropped wraps, blank renders, colour flips) and a STRUCTURAL content+typography diff (dropped/mis-slotted headings, eyebrows, CTAs; rendered-face font forks). Stack-agnostic via profiles (eds | generic). Use after converting a prototype to EDS/AEM (the stardust:deploy Step 10), or for any prototype↔build fidelity check; invocable as stardust:diff and from workflows.