'anp' 검색 결과

Voegt een proof-of-concept toe aan het poc-portaal op poc.regelrecht.rijks.app — register-entry, map-indeling, de subpad-aanpassingen die een losse app nodig heeft om onder /<slug>/ te draaien, en de bedrading in de deploy. Gebruik dit bij "voeg poc X toe", het verhuizen van een losse PoC-repo naar de monorepo, of het aanpassen van status en voorbehoud van een bestaande poc.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Scanpy is a scalable Python toolkit for analyzing single-cell RNA-seq data, built on AnnData. Apply this skill for complete single-cell workflows including quality control, normalization, dimensionality reduction, clustering, marker gene identification, visualization, and trajectory analysis.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Find biological pathways and functions enriched in gene lists or ranked gene data. Choose an appropriate statistical method, align gene identifiers, define comparison backgrounds, and turn results into interpretable tables and plots with multiple-testing corrections.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding enriched pathways among differentially expressed genes
• Running GSEA on a complete ranked gene list
• Calculating gene-set scores for individual samples or cells

Prepare bulk RNA-seq sequencing files or quantification outputs for gene-level comparisons. Check sample information and data quality, configure processing workflows, and assemble validated count tables and metadata for downstream differential expression analysis with PyDESeq2.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing gene count tables from FASTQ files
• Configuring an nf-core/rnaseq workflow
• Combining Salmon, STAR, or featureCounts outputs

Create an implementation plan grounded in code relationships and verified source files, with proposed changes, test scenarios, risks, and a structured handoff for an implementation agent. It can also revisit and strengthen an existing plan.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Planning a new feature
• Assessing a shared API change before implementation
• Strengthening and rechecking an existing plan

Understand and extend GitNexus taint analysis, which tracks data from input sources to potentially dangerous operations. Use its implementation guidance to investigate missed or incorrect findings, add detection models, and validate analysis changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating missed or incorrect data-flow findings
• Adding input sources, dangerous operations, or sanitizers
• Reviewing analysis that follows data across functions

Review pull requests, branches, commit ranges, or local changes with GitNexus. Combine code relationship analysis with source and test inspection to identify concrete defects, missing tests, affected behavior, and risks before merging.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review a pull request before merging
• Trace regressions beyond changed files
• Find missing tests for changed behavior

Rename functions, extract modules, and split or move code with dependency checks before editing and validation afterward. GitNexus previews semantic renames, meaning changes follow code bindings, and reports the scope and limits of its coverage.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Renaming a function and its references
• Extracting code into a separate module
• Splitting a large function or service

Find the right GitNexus tools and workflows for exploring code relationships. This reference explains available commands, graph queries, and resources, including how to check which branch an answer describes and whether its index is current.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find a GitNexus tool for a specific task
• Learn how to query code relationships
• Check index freshness and branch information

Carry out an engineering plan through stepwise code changes, dependency impact checks, tests, and focused commits. It also handles small, bounded tasks directly, checking the code relationship index before relying on its results.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Implementing an existing engineering plan
• Making a small change across one or two files
• Testing each step before committing

Explore unfamiliar code with GitNexus to understand project structure and execution flows. Find related functions, inspect their callers and callees, and read implementation files to explain how a feature works, with repository and index freshness information.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Understand the structure of an unfamiliar project
• Trace authentication or payment flows
• Find a function's callers and callees

Use GitNexus to inspect which conditions control a statement and how variable values flow within a function. Understand early exits, investigate empty query results, and guide changes to the tool’s control and data dependency queries.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check which conditions control a statement
• Trace a variable within a function
• Investigate empty pdg_query results

Investigate errors and unexpected behavior by finding related code, following function calls, and checking source files. GitNexus helps trace execution paths, while the diagnosis identifies the repository and reports how current its code index is.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding where an error originates
• Investigating an endpoint that returns 500
• Tracing calls between two functions

Build and maintain a GitNexus code index, a searchable map of code relationships. Use CLI commands to refresh or remove indexes, check their status, list indexed projects, and generate repository documentation with an LLM.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create a code index for a new project
• Refresh the index after code changes
• Check, remove, or list existing indexes

Assess the impact of code changes with GitNexus by tracing callers, dependencies, and affected execution flows. Check existing changes and report their scope, risk, and uncertainty before editing or committing.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking the impact of changing a function
• Finding code that depends on a target
• Reviewing affected flows before committing

Review a GitNexus pull request for production readiness with seven coordinated reviewer agents. Combine their findings and have a final critic check the draft, producing a review without editing code or posting results.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing a GitNexus pull request before production use
• Combining findings from multiple reviewer agents
• Checking a review draft before finalizing it

Coordinate a development task from planning through implementation and review. Choose whether to proceed after seeing the plan, then receive a report covering commits, verification results, review findings, and any work left unfinished.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Plan, implement, and review a feature
• Review a plan before authorizing implementation
• Start implementation from an existing plan

Turn product management notes or workshop material into a structured skill, or update an existing one. Follow a workflow covering duplicate checks, drafting, validation, catalog updates, and optional ZIP packaging for upload.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turning workshop notes into a product management skill
• Updating a skill while preserving repository standards
• Checking structure and metadata before committing

Guide a team through questions about users, workflows, and priorities to create a user story map. Organize activities and tasks, then define a minimum viable product and later releases that each cover the full workflow.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Facilitating a team story mapping workshop
• Reorganizing a flat backlog around user workflows
• Defining the scope of a minimum viable product

Turn user research and complaints into a clear problem statement. Identify who is struggling, their desired outcome, barriers, root causes, constraints, and emotional impact, then summarize the problem in one sentence for team discussions or product planning.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Agreeing on the user problem before proposing solutions
• Writing a concise problem statement for a PRD
• Finding the underlying problem behind feature requests

Evaluate SaaS customer economics and cash efficiency using acquisition costs, customer lifetime value, margins, and payback periods. Compare segments and channels, estimate how long cash will last, and assess whether to expand spending or improve efficiency.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing customer economics before increasing paid acquisition
• Comparing acquisition costs and payback across channels
• Estimating cash runway and funding needs

Track competitors' public pricing in a consistent format across repeated reviews. Compare prices, plans, feature access, usage limits, and free offers with previous records, then report documented changes and possible strategic signals with URLs and dates.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating an initial competitor pricing record
• Reviewing monthly or quarterly pricing changes
• Tracking changes to feature access and usage limits

Choose a prioritization method that fits your product stage, team, stakeholder needs, and available data. Get a recommended framework, practical setup steps, a scoring example, and an alternative approach with its tradeoffs.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choosing a method for recurring roadmap prioritization
• Selecting a lightweight approach when data is scarce
• Agreeing on prioritization rules with stakeholders

Plan how to approach a key stakeholder by examining their role, authority, concerns, and situation. Get tailored messaging, communication methods, frequency, mutual expectations, and a concrete next action with an owner and deadline.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing executive alignment before a roadmap review
• Planning a conversation with a resistant stakeholder
• Including frontline users in decisions that affect them