Results for “strict”

Turns Hi-C/Micro-C FASTQ into a deduplicated, filtered .pairs file with pairtools and decides whether the library worked. Covers the bwa mem -SP5M / bwa-mem2 / chromap --preset hic alignment idiom (mates mapped as independent single-end reads), pairtools parse vs parse2 and the walks-policy choice (5unique pairwise vs all for Pore-C/Micro-C concatemers), pair-type classification (keep UU and rescued UC), dedup (PCR vs optical/by-tile), select by pair_type/MAPQ/distance, restriction-fragment handling (restrict, Arima dual-enzyme, Micro-C/DNase fragment-free), and allele-specific phasing (pairtools phase to two coolers). The library-QC decision uses % long-range cis as the one-number quality metric, trans as the noise floor, orientation balance as fragment-map-free dangling-end/self-circle QC, and % duplicates as a complexity proxy. Use when processing Hi-C/Micro-C/Omni-C reads into pairs, judging library quality, handling multi-enzyme or restriction-agnostic protocols, or generating allele-specific contacts.

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

Implements age-gating mechanisms for online services to restrict access based on user age. Covers hard gates versus soft gates, neutral age prompts, re-verification triggers, circumvention prevention, and regulatory requirements under GDPR, COPPA, UK Online Safety Act, and DSA. Keywords: age gate, age restriction, neutral prompt, children, online services, access control.

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

Elite UX/UI & Advanced GSAP Motion Engineer. Enforces Python-driven true randomization for layout variance, strict AIDA page structure, wide editorial typography (bans 6-line wraps), gapless bento grids, strict GSAP ScrollTriggers (pinning, stacking, scrubbing), inline micro-images, and massive section spacing. Use when building motion-rich frontend pages with stricter GPT/Codex design enforcement.

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

Use this skill when designing, auditing, or troubleshooting behavioral boundaries for Agentforce agents — including topic (now subagent) Scope fields, agent-level system instructions, topic/action filters, the Escalation topic, restricted topics, and Instruction Adherence monitoring. Trigger keywords: agent guardrails, agent out of scope, restrict agent behavior, topic scope, subagent scope, agent fallback, Escalation topic, abuse prevention, action filters. NOT for Trust Layer content filtering (Einstein Trust Layer is a separate product concern), NOT for general topic routing design (use agentforce/agent-topic-design), NOT for prompt template construction (use agentforce/prompt-builder-templates).

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

Use when setting the default filtered set of records a user sees in list views, reports and SOQL without removing their access. Trigger keywords: scoping rule, Filter by scope, default record scope, RestrictionRule enforcementType Scoping, Object Manager scoping rule, recordFilter. NOT for the SOQL USING SCOPE clause - use apex/soql-using-scope-clause. NOT for blocking record access - use admin/restriction-rules.

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

Session-scoped directory edit restriction. Blocks Edit and Write outside the allowed path for the current session only. Use when debugging to prevent accidentally "fixing" unrelated code, or when you want to scope changes to one module. Use when asked to "freeze", "restrict edits", "only edit this folder", or "lock down edits". NOT for blocking destructive shell commands (see mk:careful).

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

Use only when the user explicitly requests strict code-cell-only output for a Jupyter or undergraduate data-science task, or when an ITX2007 assignment requires that format. Do not activate for ordinary data analysis or explanation requests.

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

This skill should be used when the user asks how to "use VibeTags", "add VibeTags annotations", "set up AI guardrails", "protect code from AI", "configure AI platforms", asks about @AILocked, @AIContext, @AIDraft, @AIAudit, @AIIgnore, @AIPrivacy, @AICore, @AIPerformance, @AIContract, @AITestDriven, @AIThreadSafe, @AIImmutable, @AIDeprecated, @AIObservability, @AIRegulation, @AIArchitecture, @AILegacyBridge, @AIStrictClasspath, @AIInternationalized, @AIPublicAPI, @AISchemaSafe, @AIStrictExceptions, @AIStrictTypes, @AIParallelTests, @AIIdempotent, @AIFeatureFlag, @AISecure, @AICallersOnly, @AISandboxOnly, @AIMemoryBudget, @AIPure, @AIDomainModel, @AIExtensible, @AIInputSanitized, @AISecureLogging, @AIExplain, @AIPrototype, @AISunset, @AITemporary annotations, or wants to control how AI tools interact with Java code.

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

Turns Hi-C/Micro-C FASTQ into a deduplicated, filtered .pairs file with pairtools and decides whether the library worked. Covers the bwa mem -SP5M / bwa-mem2 / chromap --preset hic alignment idiom (mates mapped as independent single-end reads), pairtools parse vs parse2 and the walks-policy choice (5unique pairwise vs all for Pore-C/Micro-C concatemers), pair-type classification (keep UU and rescued UC), dedup (PCR vs optical/by-tile), select by pair_type/MAPQ/distance, restriction-fragment handling (restrict, Arima dual-enzyme, Micro-C/DNase fragment-free), and allele-specific phasing (pairtools phase to two coolers). The library-QC decision uses % long-range cis as the one-number quality metric, trans as the noise floor, orientation balance as fragment-map-free dangling-end/self-circle QC, and % duplicates as a complexity proxy. Use when processing Hi-C/Micro-C/Omni-C reads into pairs, judging library quality, handling multi-enzyme or restriction-agnostic protocols, or generating allele-specific contacts.

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

Write type-safe TypeScript code with strict mode enabled, comprehensive type definitions, proper error handling, and elimination of any types. Use when enabling TypeScript strict mode, adding types to existing JavaScript, fixing type errors, creating type definitions, using utility types, implementing type guards, avoiding any types, creating generic types, or ensuring complete type safety across the codebase.

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

Turns Hi-C/Micro-C FASTQ into a deduplicated, filtered .pairs file with pairtools and decides whether the library worked. Covers the bwa mem -SP5M / bwa-mem2 / chromap --preset hic alignment idiom (mates mapped as independent single-end reads), pairtools parse vs parse2 and the walks-policy choice (5unique pairwise vs all for Pore-C/Micro-C concatemers), pair-type classification (keep UU and rescued UC), dedup (PCR vs optical/by-tile), select by pair_type/MAPQ/distance, restriction-fragment handling (restrict, Arima dual-enzyme, Micro-C/DNase fragment-free), and allele-specific phasing (pairtools phase to two coolers). The library-QC decision uses % long-range cis as the one-number quality metric, trans as the noise floor, orientation balance as fragment-map-free dangling-end/self-circle QC, and % duplicates as a complexity proxy. Use when processing Hi-C/Micro-C/Omni-C reads into pairs, judging library quality, handling multi-enzyme or restriction-agnostic protocols, or generating allele-specific contacts.

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

Review healthcare applications for exposure of patient and staff information. Classify sensitive data, design access restrictions for individual database rows, record data access and changes, and check common leaks through logs, URLs, and browser storage.

• Review code that handles patient records
• Design access restrictions between healthcare facilities
• Record access to and changes in sensitive data

Enable warnings for destructive commands and restrict file edits to a chosen directory. It combines /careful and /freeze to help control work on live systems, while blocking certain catastrophic command patterns outright.

• Restricting edits during production work
• Keeping live debugging within one directory
• Warning before deletion or force-push commands

Limit file edits to a chosen directory and block Edit, Write, and NotebookEdit operations outside it. Keep debugging or module changes within scope, with the restriction remaining active until explicitly removed.

• Keeping debugging edits within one folder
• Limiting changes to a single module
• Preventing accidental edits to unrelated files

Design desktop landing page prototypes with varied layouts, large typography, dense grids, and GSAP animations tied to scrolling. Pages follow an attention-to-action structure, with explicit checks for heading length, grid completeness, and button text contrast.

• Prototyping a landing page with scroll animations
• Exploring varied hero layouts and typography
• Designing a compact grid without empty cells

Manage OmniRoute API keys and provider authentication from the command line. Register, rotate, or revoke keys, inspect usage and expiration, set spending and model restrictions, and start or check OAuth sign-in connections.

• Registering provider API keys and listing existing keys
• Rotating keys with a grace period or revoking them
• Checking usage and setting spending or model restrictions

Inspect OmniRoute connection restrictions, usage quotas, and retry delays from the command line. Reset stuck providers and adjust failure thresholds, cooldowns, and recovery timing to manage how connections respond to errors.

• Investigate connection restrictions after errors
• Reset stuck providers or connections
• Adjust failure thresholds and retry delays

Track documented code fixes across releases with a signed manifest, a list of fixes and their identifying text. Verify that markers remain in source files, inspect file changes, and use recorded history to identify commits associated with regressions.

• Check that documented fixes remain before a release
• Trace a regression through release history
• Verify signed fix records in CI

Review HTTP response headers and restrict browser features an application does not need, such as camera, microphone, and location access. Guide Permissions-Policy settings that limit what attackers could use if the site is compromised.

• Review security headers before a release
• Disable unused camera and microphone features
• Check feature restrictions for third-party iframes

Audit important pages for settings that hide descriptions in Google search results. Check robots meta tags and response headers, report affected URLs, and adjust snippet controls after confirming whether the restriction is intentional.

• Investigating missing descriptions in search results
• Auditing snippet settings on key landing pages
• Reviewing robots tags and response headers

Review form fields for code that blocks pasting, then remove those restrictions. The skill helps check password manager use, keyboard interactions, and accessibility so people can paste passwords and other long values into inputs.

• Checking why passwords cannot be pasted
• Reviewing credit card fields for paste restrictions
• Improving form accessibility

Review HSTS, a browser policy that keeps site connections on HTTPS. Check response headers, policy duration, and subdomain coverage, guide server or CDN configuration, and explain the precautions needed before enabling browser preloading.

• Checking HSTS headers on HTTPS responses
• Configuring HSTS on a web server or CDN
• Reviewing policy duration and subdomain coverage

Test REST, GraphQL, and gRPC APIs with Strix using schemas, credentials, and example data. Investigate authorization flaws, excessive data exposure, and other API risks, then verify findings with requests that reproduce the issue.

• Testing an API from its specification
• Checking data access across tenants
• Verifying restrictions on administrator routes

Review which actions are available in each of four Remotion Studio modes. Use these distinctions when implementing or checking interface controls, so actions that depend on a server are hidden or disabled where the mode cannot support them.

• Check mode support before adding a Studio action
• Review controls in a deployed Studio
• Check behavior after the preview server disconnects