Results for “technology”

Technical research methodology with YAGNI/KISS/DRY principles. Phases: scope definition, information gathering, analysis, synthesis, recommendation. Capabilities: technology evaluation, architecture analysis, best practices research, trade-off assessment, solution design. Actions: research, analyze, evaluate, compare, recommend technical solutions. Keywords: research, technology evaluation, best practices, architecture analysis, trade-offs, scalability, security, maintainability, YAGNI, KISS, DRY, technical analysis, solution design, competitive analysis, feasibility study. Use when: researching technologies, evaluating architectures, analyzing best practices, comparing solutions, assessing technical trade-offs, planning scalable/secure systems.

The English summary is being prepared. Showing the original description.

Library of accessibility personas representing people with various disabilities, impairments, and situational limitations. Use this skill when users ask about disability types, accessibility personas, user needs for specific conditions, how people with disabilities use technology, assistive technology users, or designing for accessibility. Triggers on requests about blindness, deafness, cognitive disabilities, motor impairments, low vision, screen readers, sign language, autism, ADHD, temporary disabilities, or any question about "how would a person with X use this".

The English summary is being prepared. Showing the original description.

Comprehensive technology-agnostic prompt generator for documenting end-to-end application workflows. Automatically detects project architecture patterns, technology stacks, and data flow patterns to generate detailed implementation blueprints covering entry points, service layers, data access, error handling, and testing approaches across multiple technologies including .NET, Java/Spring, React, and microservices architectures.

The English summary is being prepared. Showing the original description.

Comprehensive technology-agnostic prompt for analyzing and documenting project folder structures. Auto-detects project types (.NET, Java, React, Angular, Python, Node.js, Flutter), generates detailed blueprints with visualization options, naming conventions, file placement patterns, and extension templates for maintaining consistent code organization across diverse technology stacks.

The English summary is being prepared. Showing the original description.

Technology-agnostic blueprint generator for creating comprehensive copilot-instructions.md files that guide GitHub Copilot to produce code consistent with project standards, architecture patterns, and exact technology versions by analyzing existing codebase patterns and avoiding assumptions.

The English summary is being prepared. Showing the original description.

Expert database architect specializing in data layer design from scratch, technology selection, schema modeling, and scalable database architectures. Masters SQL/NoSQL/TimeSeries database selection, normalization strategies, migration planning, and performance-first design. Handles both greenfield architectures and re-architecture of existing systems. Use PROACTIVELY for database architecture, technology selection, or data modeling decisions.

The English summary is being prepared. Showing the original description.

Research a topic across multiple web sources, break it into focused questions, and read key pages in depth. Produce a report with source links, confidence levels, practical findings, and clear distinctions between facts and estimates.

• Investigating competitors and market trends
• Comparing technologies before choosing one
• Researching market size and growth forecasts

Build a project-specific ECC installation plan using evidence from code and configuration. Sort skills, rules, hooks, and other components into items loaded every session and references kept available for occasional use.

• Select ECC components that match a project's technology
• Separate everyday tools from occasional references
• Clean up outdated language rules and incompatible hooks

Measure web page speed, API response times, and build or test duration. Save baseline measurements as JSON tracked in Git, then compare results before and after changes to identify performance regressions and assess launch targets.

• Comparing performance before and after a code change
• Investigating reports that a page feels slow
• Checking performance targets before launch

Design and audit interfaces for Web, iOS, and Android using WCAG 2.2 accessibility guidance. Check screen-reader labels, keyboard navigation, contrast, and control sizes to identify barriers and guide implementation for people using assistive technology.

• Adding descriptive labels to icon-only buttons
• Reviewing keyboard navigation and modal focus
• Checking contrast and control sizes

Search local design guidance to plan, build, review, or improve web, mobile, and desktop interfaces. Find suitable colors, font pairings, layouts, charts, and interaction patterns, with implementation advice matched to the project's technology.

• Choose colors and fonts for a new product
• Review forms and keyboard accessibility
• Fix layouts that break on small screens

Create full-screen animated visuals with WebGL, a browser technology for GPU rendering. Combine shaders, 3D scenes, or particles with a text overlay, and deliver the result as one self-contained HTML file without external requests.

• Create a website hero animation
• Build generative art with a headline
• Prototype a 3D scene or particle field

Audit and improve an existing website or app's interface while preserving its functionality and technology stack. Refine typography, colors, layout, and interaction states through focused changes, checking functionality after each update.

• Audit an existing website's visual design
• Replace repetitive, generic interface patterns
• Improve loading, empty, and error states

Get a plain-English explanation of a technical topic, organized around who is involved, what it is, where it applies, why it matters, and when it is used, so you can understand its basic context.

• Understanding an unfamiliar technical topic
• Learning where and when a technology is used
• Clarifying who is involved and why something matters

Browse World Monitor's curated news feeds by topic or language, with duplicate stories removed. Review headlines, sources, publication dates, threat labels, and alert flags, then summarize selected headlines or translate them through the connected tools.

• Scanning current headlines across topics
• Reviewing technology or finance news by language
• Summarizing or translating selected headlines

Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.

• Record the reasoning behind adopting a technology
• Start an ADR for an API or data model change
• Document an infrastructure decision

Review HTML object elements and add meaningful fallback content for people who cannot load or view embedded material. Identify missing alternatives, suggest text or appropriate HTML elements, and explain how to verify accessibility.

• Find object elements with missing fallback content
• Add alternatives for embedded content that fails to load
• Review whether fallback content conveys equivalent information

Compare button and link text with accessible names, the names assistive technology uses for controls. Identify mismatches and suggest ARIA label changes so people using voice control can refer to the words they see.

• Comparing visible button text with accessible names
• Reviewing links that are hard to activate by voice
• Checking label fixes with accessibility tools

Review whether interactive web elements work with keyboard navigation. Check Tab order, hidden elements, and focus traps where users cannot move away, then identify specific fixes and ways to verify behavior with browser accessibility tools or assistive technology.

• Check whether all controls are reachable with Tab
• Align keyboard focus order with the visual reading order
• Remove hidden content from the Tab sequence

Review a page to ensure it has exactly one main landmark, the region identifying its primary content. Find missing or duplicate main regions and get corrections that give assistive technology users a clear navigation target.

• Checking the main region in a page template
• Fixing duplicate main regions in combined layouts
• Reviewing navigation to primary content with a screen reader

Check HTML for meta refresh redirects that can interrupt reading and confuse users. Suggest server-side redirects or clear links users choose themselves, with guidance for checking the resulting behavior using accessibility tools or assistive technology.

• Finding automatic redirects in HTML
• Replacing meta refresh with server-side redirects
• Reviewing page transitions for screen reader users

Review iframe and frame titles so screen reader users can identify embedded content before entering it. Find missing or empty title attributes, add meaningful descriptions, and verify the changes with browser accessibility tools or assistive technology.

• Checking titles on embedded advertisements and social media widgets
• Reviewing missing or empty iframe title attributes
• Verifying frame identification with a screen reader

Review decorative images and icons to prevent unnecessary screen reader announcements. Check empty alt text, aria-hidden, and relevant keyboard behavior, then suggest fixes for concrete accessibility issues without flagging decorative assets solely because they exist.

• Checking decorative images for unnecessary announcements
• Reviewing accessibility of SVGs and icons
• Checking shared decorative component patterns

Review rendered HTML for duplicate IDs used by ARIA attributes, which connect elements to labels and descriptions for assistive technology. Identify ambiguous references, correct IDs and their links, and explain how to verify the changes.

• Investigating incorrect labels read by screen readers
• Checking repeated components for duplicate IDs
• Reviewing ARIA references in a design system