Results for “pr”

Pre-writing interview that captures the author's real opinions, experiences, and stances on a blog topic before the post is written on their behalf — the companion that runs BEFORE seo-blog-writer. Use this skill automatically whenever a blog post or article is about to be drafted under the user's name or brand — run the topic interview first, then hand the resulting Opinion Packet to seo-blog-writer. Also use it when the user says "interview me about this topic", "get my take first", "ask me what I think", or "update my opinion bank". Scope: blog/article topics only — not emails, docs, social posts, or other writing. If a blog post is about to be written as the user's voice and their take on the topic hasn't been captured, this skill triggers — even if they only asked for "a blog post about X".

Make sure to use this skill whenever the user mentions anything related to Danish job listings, job search in Denmark, finding work in Denmark, or job vacancies on Jobdanmark — even if they don't explicitly mention jobdanmark.dk. Also invoke this skill for questions about specific Danish job categories, municipalities, job types, or salaries in a job-search context. Trigger phrases include: danish jobs, jobs in denmark, find job denmark, job search denmark, danish job listings, jobdanmark, job opslag, find job, jobsøgning, ledige stillinger, stillingsopslag, job i Danmark, fuldtidsjob, deltidsjob, studiejob, praktikplads, elev, fleksjob, IT job denmark, sygeplejersker job, håndværker job, ingeniør job, pædagog job, kontor job, leder job, salg job, hotel job, kirke job, job aarhus, job københavn, job odense, job aalborg, job sjælland, job jylland, job fyn, jobkategorier denmark, ledige job, ansøgningsfrist, søg job, job opslaget, jobopslag, danish vacancies, work in denmark, employment denmark, job denmark, jo

The art and science of arranging type to make written language legible, readable, and visually appealing. Typography is the invisible art - when done well, readers absorb content without noticing the craft. When done poorly, they struggle without knowing why. Great typography creates visual hierarchy, establishes rhythm, conveys emotion, and guides the eye through content. It combines centuries of print wisdom with modern digital constraints - understanding that a typeface designed for books may fail on screens, that line length affects comprehension, and that the space between letters matters as much as the letters themselves. This skill covers type selection, pairing, scaling, spacing, responsive typography, variable fonts, font loading optimization, and accessibility. Master typographers know that choosing a font is the easy part - the craft is in the details of how it's set. Use when "typography, font, typeface, type scale, line height, leading, kerning, tracking, font pairing, font loading, variable font

World-class color theory expertise combining the scientific precision of Josef Albers' "Interaction of Color," the systematic thinking of color systems from Pantone and RAL, and the perceptual psychology insights from researchers like Bevil Conway. Color is not just aesthetics - it's communication, emotion, and usability compressed into wavelengths. Great color work is invisible when done right. Users don't notice "nice colors" - they notice when they can't read text, when buttons don't look clickable, when errors don't feel urgent, or when the interface feels "off" without knowing why. Color theory is the science of making the right thing feel obvious. Use when "color theory, color palette, color scheme, color harmony, complementary colors, analogous colors, contrast ratio, dark mode colors, light mode, color tokens, semantic colors, color accessibility, color blindness, color psychology, color system, brand colors, data visualization colors, color, design, accessibility, contrast, dark-mode, theming, tokens

Expert content repurposing skill for creators and professionals who want to get more out of content they've already created. Use this skill whenever the user wants to turn one piece of content into multiple formats — for example: turning a blog post into social media posts, converting a YouTube video or podcast into a newsletter or article, transforming a long-form piece into short clips or quotes, or adapting any content for a different platform or audience. Triggers: "repurpose this", "turn this into a post", "make a LinkedIn post from this", "convert this blog to a tweet thread", "I have a video/podcast, can you make it into a newsletter", "get more out of this content", "adapt this for [platform]", or any request to transform existing content into a new format. Do NOT limit to obvious repurposing requests — if the user shares content and mentions another platform or format, use this skill.

Build work collaboratively in reviewable pieces, handing each piece back for review before starting the next, so the person stays in the lead and steers while the work happens instead of reviewing a finished result. Use when someone says to pair with them on something, asks to collaborate rather than direct, wants to review as it goes, or wants to guide the work piece by piece — on code, on a design decision, or on writing. For a test-first build it runs tdd, for restructuring it runs refactor, for an interface contract it runs design-an-api, and for plan work it runs iterative-plan-review or plan-implementation, each collaboratively; invoke any of those directly instead to run it straight through without pausing. Does not pace someone through code that already exists and builds nothing — use code-walkthrough. Does not explain, summarize, or research something instead of producing it — use code-overview or research.

Build editorial/magazine/report webpages on a GENUINE Müller-Brockmann modular grid (International Typographic Style), not a decorative one. Encodes the discipline — columns + modules + baseline, grotesque type, flush-left ragged-right, restrained black/white/red — AND the front-end engineering that makes the grid load-bearing: one CSS-variable source of truth, a grid-toggle overlay that lives in the SAME content box as the content, subgrid 'bands' so every element snaps to a column line, an 8px baseline lock, and runtime optical alignment that puts display type's ink (not its box) on the line. Ships a scaffold generator and a Puppeteer harness that proves 0px adherence. Use when: building any editorial, magazine, report, or longform page that must read as rigorously grid-aligned, Swiss, International Typographic Style, or 'Müller-Brockmann'. Triggers: magazine spread, grid system, Swiss design, editorial layout, show the grid, grid overlay toggle, baseline grid, modular grid, 12-column layout, 瑞士网格, 版面网格.

Simulator.Company task & assignment specialist — creating a task and assigning who does it, who approves it, and whose signature it needs. In Simulator a task is an actor of the Events system form (no chatType), and the roles are access privileges, not data fields: the executor gets `execute`, approvers get `sign`, and a legal document's signers get `ds`. Completion and sign-off are then posted as `done` / `sign` / `reject` reactions. Use when the user wants to "create a task", "assign a task to", "set an executor/assignee", "add approvers", "require a signature", "who signs this", "make a to-do". Also covers **order / directive documents** that tell a specific person to do something — an "order/наказ addressed to X" is a task whose addressee is the executor. Activate on "create a task", "assign to", "task for", "needs approval", "who approves", "requires signature", "sign-off", "order", "decree", "directive", "create an order for", "створи задачу", "постав задачу", "признач виконавця", "додай погоджувача", "

Audit a landing page or marketing site through one lens: what is the ONE thing this page wants the visitor to do, and does every element on the page move them toward it? Reconstructs who lands on the page and why, spawns visitor-persona agents to react to it cold, maps the belief chain a visitor must climb before acting, inventories CTAs and everything competing with them, then delivers a prioritized cut/move/add/rewrite plan. Use whenever the user asks "what do we want people to do on this page", "is this page converting", "critique this landing page", "why would someone book/buy/sign up here", "audit the funnel on X page", or wants strategic critique of page content and structure (not visual polish). Works from frontend code in a repo, a live URL via browser tools, or pasted copy/screenshots. Judges persuasion and intent-alignment; for flow usability and friction use ux-audit, for visual and aesthetic quality use the impeccable critique/audit skills.

Anti-slop frontend design skill for building NEW landing pages, portfolios, and UI from a brief. Reads the brief and existing brand context first, infers a design direction from three configurable dials (variance, motion, density), and ships interfaces that don't look templated or default-AI. Use when starting a new page/UI with no existing identity to preserve, or when asked to design something "that doesn't look like every other AI landing page." For auditing and upgrading an EXISTING UI, use `taste-redesign` instead — this skill is for the moment before code exists. Triggers on: "build a landing page", "design a portfolio", "make this not look generic/templated/AI-generated", "anti-slop", starting UI work with a brief but no established identity yet. Also owns component-library selection (which package for toasts, dropdowns, charts, drag-and-drop, state, etc.) — use this instead of hand-rolling a component or guessing at a dependency. Source: github.com/Leonxlnx/taste-skill (taste-skill, the main v2 varian

Create, set up, or update the personal context portfolio: structured markdown files describing who you are, how you work, your teams, and your tool/ADO configuration. Runs the interview workflow for first-time setup and targeted edits for updates. Trigger this skill when the user asks to: set up their context, create or update their context portfolio, "create my IQ", "set up my IQ", edit their profile, add/remove a stakeholder, update ADO config, change team info, update pillars, or set up any plugin configuration. Trigger when another skill fails to find context (missing files or TODO markers) and needs context populated. Also trigger when the user mentions a context change in passing (e.g., "my manager changed", "we added someone to the team") to offer a context file update. Do NOT trigger for read-only questions like "who's on my team?" or "what's my ADO config?". Those are answered directly from the context files referenced in the loaded custom instructions; no skill is needed.

Use when a human asks to connect to or enter Agent Internet or AI Internet, get their agent online, or open Agent Internet Browser, Bot Browser, a Bot page, a Bot homepage, a domain alias, a chain pin, a MetaApp, a MetaFile, or a map through the existing local Browser entrypoint, including opening a resource in a new Browser tab; also use when the human wants to find or discover on-chain MetaApps by topic, tag, publisher, or time range — such as "what on-chain mini-games exist", "apps published in the last 30 days", or "open the on-chain buzz app" — list the remixes of a known app, read what an app does, or remix and republish an existing MetaApp; also use when the human wants to find or discover on-chain users or Bots by name, personality, skill, or recency — such as "view Alice's bot page", "find cheerful users to chat with", or "find a bot that can translate" — or read an identity's full on-chain profile.

Cut a Han release: update CHANGELOG.md with the changes since the last release, bump every plugin that changed, tag every plugin as {plugin-name}--v{version} so a version-constrained dependency can resolve, and publish a GitHub release whose notes attribute every merged pull request to its author, credit every closed issue to the person who opened it, the people who contributed to it, and the people who worked on the fix, and link back to the full changelog for that version. Han ships as a parent meta-plugin (`han`) plus child plugins (`han-core`, `han-github`, `han-reporting`, and any future `han-*` extension); the skill versions each plugin independently and tags each one independently, with the release attaching to the parent's tag. Use when releasing, cutting a release, shipping a new Han version, publishing release notes, or tagging a version. Reads each plugin's target version from its plugin.json; when a plugin has not been bumped past the latest tag yet, it proposes a semantic-versioning bump and conf

이미 굴러가는 저장소에서 코드를 바꾸는 요청이면 크기와 무관하게, 파일을 건드리기 전에 이 스킬로 GitHub 이슈부터 등록합니다. 반대로 빈 폴더나 방금 git init 한 프로젝트에 package.json·tsconfig·lint 설정·기본 레이아웃 같은 초기 뼈대를 세우는 일은 여기 해당하지 않으니 그냥 만들어 주세요. 기능 추가, 버그 수정, 화면이 깨지거나 안 보이거나 잘리거나 새로고침하면 초기화되는 문제, 중복 호출·느린 응답 같은 동작 개선, 안 쓰는 코드·플래그·스크립트 삭제가 전부 해당합니다. 증상만 적어 보낸 버그 리포트, "이거 지워도 될까?" 처럼 물음표로 끝나는 정리 요청, 특정 파일·컴포넌트를 콕 집어 고쳐 달라는 요청도 똑같이 해당합니다. 사용자가 고칠 파일 경로와 구현 방법까지 지정해 줬더라도 바로 편집에 들어가지 않고 이슈부터 만듭니다. 사용자가 "이슈" 를 한 마디도 꺼내지 않아도, 요청이 한 줄짜리로 보여도, 이슈 번호가 함께 오지 않았다면 코드를 읽기 전에 먼저 이 스킬을 탑니다. 한 요청에 독립 작업이 여러 개 섞여 있으면 그만큼 이슈를 나눠 만듭니다. 저장소가 이슈를 만들 단계인지 판정하고, 항목마다 유사 이슈를 검색하고, issue-start 가 그대로 이어받을 형식으로 초안을 만들어 승인받고 라벨과 함께 등록합니다. 등록을 마친 뒤에는 라벨이 빠진 기존 이슈까지 이어서 점검해 보정합니다. `~/.issue/settings.json`의 `issue.createMode`가 `direct`면 암묵적으로 발동한 뒤 조용히 빠져 원래 변경 요청을 계속하지만, `$issue-create`, "이슈 만들어줘", "이슈부터 등록" 같은 명시 요청에는 설정과 관계없이 씁니다. 이미 이슈 번호를 받은 착수 요청은 issue-start, 구현이 끝나 증거·PR 차례면 issue-end, 워크트리 통합은 issue-merge 를 쓰고, 코드는 그대로 둔 채 이슈 목록 조회나 라벨 정리만 원하거나 커밋이 거의 없는 새 스캐폴딩 프로젝트라면 쓰지 않습니다.