Loading...
Loading...
Found 157 Skills
9-phase Development Pipeline complete knowledge. Use when user doesn't know development order or starts a new project from scratch. Use proactively when user asks about development order, phases, what to do first, or starts a new project without clear direction. Triggers: development pipeline, phase, development order, where to start, what to do first, how to begin, new project, 개발 파이프라인, 뭐부터, 어디서부터, 순서, 시작, 開発パイプライン, 何から, どこから, 开发流程, 从哪里开始, pipeline de desarrollo, fase, orden de desarrollo, por dónde empezar, qué hacer primero, pipeline de développement, phase, ordre de développement, par où commencer, que faire d'abord, Entwicklungspipeline, Phase, Entwicklungsreihenfolge, wo anfangen, was zuerst tun, pipeline di sviluppo, fase, ordine di sviluppo, da dove iniziare, cosa fare prima Do NOT use for: ongoing implementation, existing feature work, or bug fixes.
Make sure to use this skill whenever the user mentions anything related to Danish property data, housing prices, real estate statistics, sold homes, property history, BBR data, or the Danish housing market — even if they don't mention boliga.dk explicitly. Also invoke this skill for questions about specific Danish addresses, zip codes, or municipalities in a housing context. Trigger phrases include: danish property, danish real estate, danish housing market, boliga, bolig til salg, solgte boliger, boligpriser, ejendomspriser, ejendom, ejerlejlighed, villa, rækkehus, sommerhus, fritidshus, andelsbolig, helårsgrund, landejendom, BBR data, bygningsregistret, property for sale denmark, sold homes denmark, house prices denmark, apartment prices copenhagen, aarhus housing, odense real estate, housing statistics denmark, quarterly price index denmark, most viewed properties denmark, property valuation denmark, ejendomsvurdering, salgspris, kvadratmeterpris, days on market, dage til salg, boligsøgning, address lookup denmark, property history denmark.
Use when user asks about 1 Staat, State - Constitutional Law, Bundesverfassung, BV, constitutional, Bürgerrecht, citizenship, Staatsrecht, Behörden, authorities, Parlament, Bundesrat, Bundesgericht, SR 1xx. Covers SR category 1 of the Systematische Rechtssammlung.
Use when user asks about 2 Privatrecht, Private Law, ZGB, OR, Zivilgesetzbuch, Obligationenrecht, civil code, contract law, Privatrecht, Handelsrecht, commercial law, SR 2xx. Covers SR category 2 of the Systematische Rechtssammlung.
Develop custom React + Vite webapps in Steedos packages (webapps/ directory). Build custom amis Renderer components via IIFE compilation, with JSX runtime shimming (amisRequire), CSS scope isolation (postcss-prefix-selector), ScopedContext registration, Express router for SPA access, Tailwind v4 workarounds, and multi-webapp management. Covers vite.amis.config.ts, amis-entry.ts, amis-jsx-shim.ts, client loader files (main/default/client/*.client.js with waitForThing/loadJs/loadCss), build scripts, and deployment to public/.
Analyze job roles for fit, draft application question responses, find hiring managers, and create follow-up emails for RYLLC job applications. Focuses on climate tech IC product/SRE roles.
Generate a Dynatrace Gen 3 **KPI dashboard** (15–20 business KPIs, required map tile, branded section dividers) and a matching 30‑minute BizEvents injector for a named company, then deploy both via `dtctl`. Use this skill ONLY when the user explicitly asks for a Dynatrace KPI dashboard, business-event KPI demo, BizEvents injector, or a "KPI dashboard for <company>" — do NOT use for generic Dynatrace dashboards (SRE, infra, k8s, services, RUM) or for editing existing non-KPI dashboards. Triggers include phrases like "generate a KPI dashboard", "build a BizEvents demo for <company>", "spin up a KPI dashboard + injector", "/generate-kpi-dashboard". Requires `dtctl` authenticated to a Dynatrace Gen 3 tenant.
Guides Site Reliability Engineering—SLI/SLO and error budgets, reliability dashboards and burn-rate alerting, production readiness reviews, capacity planning for availability, toil reduction, dependency and failure-mode analysis, release reliability (canaries, rollback criteria), and service-owner incident mitigation tied to customer impact. Use when defining or operating SLOs, measuring error budget burn, improving service reliability, running PRRs before launch, planning scalable resilient capacity, or leading technical mitigation during outages—not for CI/CD pipeline implementation (devops), incident program and paging policy design (incident-management-engineer), cloud access and patch tickets (cloud-system-administrator), load-test profiling (performance-engineer), rollout cutover strategy (deployment-strategist), or greenfield cloud build-out (cloud-engineer).
Track AI engine brand narratives. Use when: detecting narrative drift, misrepresentation, or competitor narrative gains over time.
Use this skill when integrating, configuring, or extending Modern Admin (`@modern-admin/*`) in a host project — i.e. wiring `ModernAdminModule.forRoot`, adding admin resources, configuring Better Auth/Prisma/Redis, declaring properties or `@Action`/`@Before`/`@After` hooks, setting up role permissions (`MaRole.permissions`), or troubleshooting auth/SPA 404s. Triggers on tasks that mention `@AdminResource`, `AdminController`, `adminSource`, `BetterAuthProvider`, `ModernAdminStaticUiModule`, `setupPrismaSystem`, `MaRole`, `rolesResourceId`, the `ma_*` schema fragment, or scaffolding `bun create @modern-admin`.
Search 10 academic paper databases via REST APIs for research papers, preprints, and scholarly articles. Covers PubMed, PMC (full text), bioRxiv, medRxiv, arXiv, OpenAlex, Crossref, Semantic Scholar, CORE, Unpaywall. Use when searching for papers, citations, DOI/PMID lookups, abstracts, full text, open access, preprints, citation graphs, author search, or any scholarly literature query. Triggers on mentions of any supported database or requests like "find papers on X" or "look up this DOI".
Disaster recovery drill exercises and security checklists for web application projects (SPA, SSR, full-stack web apps). Focused on solo/indie developers using free-tier infrastructure (Vercel, Supabase, Cloudflare, Netlify, Railway, etc.). Bridges big-tech best practices (NIST, Google SRE DiRT, ISO 22301) to indie scale. Use when the user mentions drills, disaster recovery, security audit, incident simulation, project health check, resilience testing, backup strategies, secret rotation, or incident response for web projects. Not for mobile apps, desktop software, CLI tools, or games.