70 skills · sorted by relevance
Design or review a system’s overall structure, compare technology choices, and plan for growth and failures. Produce architecture diagrams and Architecture Decision Records, documents that explain key choices, alternatives, and their consequences.
Create competitor comparison and alternative pages for search traffic and sales conversations. Organize product research into reusable profiles, then develop page copy, comparison tables, migration guidance, and recommendations that explain which option fits each audience.
Create competitor comparison and alternative product pages for search visibility and sales conversations. Organize verified research into page copy, comparison tables, audience recommendations, and migration guidance that help readers evaluate their options.
Document a technical decision in an architecture decision record, or ADR. Capture its context, alternatives, and consequences, assign a record number, and distinguish a proposed decision from an accepted one so dependent work reflects its actual status.
Make system architecture decisions by clarifying requirements and constraints, comparing benefits and drawbacks, and considering simpler alternatives. Record the reasoning in ADRs, architecture decision records, so significant choices and their rationale are documented.
Build a Solution Blueprint for a Dynamics 365 Finance and Supply Chain Management implementation through guided interviews. Define scope and architecture, compare options, and document decisions, their rationale, assumptions, and unresolved questions across working sessions.
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' or 'competitive landing pages.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables.
The English summary is being prepared. Showing the original description.
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' or 'competitive landing pages.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables.
The English summary is being prepared. Showing the original description.
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' or 'competitive landing pages.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables.
The English summary is being prepared. Showing the original description.
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' or 'competitive landing pages.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables.
The English summary is being prepared. Showing the original description.
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' or 'competitive landing pages.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables.
The English summary is being prepared. Showing the original description.
Record software design decisions as numbered Markdown files, with context, rejected alternatives, benefits, drawbacks, and risks. Maintain an index and consult existing ADRs—architecture decision records—to explain why a framework, database, or design approach was chosen.
Write an architecture decision record, a document explaining a team's design choice. Capture the context, rejected alternatives, and future costs so newcomers can understand the reasoning, then review the draft before saving it.
Guides the use of RWKV, a language model architecture that carries information forward in a compact state. Covers streaming text generation, long document processing, fine-tuning, and memory comparisons with Transformers.
Compare technology options, review a system design, or plan a new component from requirements and constraints. The skill organizes the reasoning into an architecture decision record, a document covering alternatives, trade-offs, consequences, and next steps.
Compare technology options, review a system design, or plan a new component from requirements and constraints. The skill organizes the reasoning into an architecture decision record, a document covering alternatives, trade-offs, consequences, and next steps.
Document a settled architecture choice as an ADR, a record of a design decision. Capture its context, rejected alternatives, benefits, costs, and links to earlier decisions it replaces so future readers can understand the reasoning.
Document why software decisions were made, which alternatives were considered, and what trade-offs remain. Create architecture decision records, README guidance, API documentation, and changelogs that help future contributors and AI agents understand the project.
Document major technical choices as Architecture Decision Records, or ADRs. Capture the context, alternatives, reasons, and consequences, then organize related records and track whether decisions are proposed, accepted, retired, or replaced.
Make system design decisions by clarifying requirements, identifying constraints, and comparing the benefits and drawbacks of different approaches. Record the reasoning in architecture decision records, or ADRs, while considering simpler alternatives and the team's experience.
Document major technical decisions with their context, alternatives, reasoning, and consequences. The skill provides Architecture Decision Record templates and maintenance practices so teams can review past choices, track replacements, and explain decisions to new members.
Implement Mamba, a model architecture that processes sequences through an internal state with computation scaling linearly with input length. Covers pretrained text generation, Mamba-1 and Mamba-2 configuration, speed comparisons with Transformers, and GPU memory troubleshooting.
Guides you through setting up RWKV, generating text, processing long documents in chunks, and fine-tuning models. Explains how to carry context between steps and compare memory use with Transformer models.
Plan AI-assisted SEO, from keyword research and competitor comparison pages to content production using data and templates. It also guides content changes for AI search citations, tool selection, quality checks, and ongoing performance tracking.