Testing & Security skills

Convert, rewrite, port, or redesign software from another language (PHP, TypeScript/JavaScript, Python, C, Go, Rust, Java, C#, …) into idiomatic, full-feature Salam: write new Salam code, and port C to Salam (including self-hosting the Salam compiler itself). Use whenever the request mentions "Salam" (the programming language / زبان سلام), a `.salam` file, "convert/port/ rewrite X to Salam", "rewrite the compiler in Salam", the Salam layout DSL, or building with the `salam` compiler. Covers both English Salam (Part I) and Persian Salam, سلام فارسی (Part II: every keyword, type, method and std package name). This is the authoritative, up-to-date reference for Salam's current syntax, its standard library, its strict compiler rules, the layout DSL, and porting low-level C. The tutorial books under `books/` are OUT OF DATE. Trust this file, `std/`, `tests/`, and the Persian course at https://www.salamlang.ir/learn/ instead.

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

What things get called. A file is named after its export in the project's case convention, a suffix is a resolution instruction rather than decoration, an index file only re-exports, and some symbol names are always wrong (utils, helpers, V2, Enhanced, New). Covers learning a tree's local vocabulary before adding to it, test and platform-variant naming, and the per-language conventions. Use when creating a file or directory, naming a test file, adding a platform variant, or when a name has to change. Triggers - "what should I call this file", "where does this file go", "naming convention", "kebab or camel", "name this test".

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

Write cargo tests. A test name is a sentence, the body is setup, mock, test and verify blocks separated by blank lines with no comments, and shared setup lives in a named test-support module rather than in each test. Covers naming, the block shape, where a test file goes, async and time, workspaces, and running one crate or one filter. Use when adding or changing any #[test] or #[tokio::test], or when Rust coverage has to come up. Triggers - "write a rust test", "cargo test", "test this crate", "cover this handler".

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

Security guidance and vulnerability review for codebases, APIs, services, CLI tools, libraries, and daemons. Use for security questions, focused reviews, vulnerability research, security audits, or pen tests. Run the complete workflow only for explicit codebase audit or pen-test requests, full/comprehensive/end-to-end reviews, or requested report artifacts.

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

Write the failing test before the code that satisfies it, for new behaviour and for bug fixes, and stop when the test path is not worth its cost. Covers the red-green loop, what a first test should assert, when to skip the loop honestly, and the evidence to report. Use when starting behaviour that has a cheap test path, or fixing a bug that can be reproduced in a test. Triggers - "tdd", "write a failing test first", "regression test", "reproduce this in a test", "test first".

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

Write TypeScript tests. A test name is a sentence, the body is setup, mock, test and verify blocks separated by blank lines with no comments, and the runner's config decides where the file goes. Covers naming, the block shape, size, fixtures, what not to assert, DOM opt-in, multiple runner projects, coverage, and running one test. Use when adding or changing any .test.ts or .test.tsx, or when coverage has to come up. Triggers - "write a test", "add tests", "test this", "vitest", "jest", "how do I test", "cover this file".

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

Develops B2B SaaS positioning from your ICP, competitor and win-loss evidence. Maps what buyers compare you to, chooses between leading with a category or a problem, picks a primary and secondary anchor and up to three defensible differentiators, lays out 2 to 4 worked positioning options with a comparison canvas so you can decide, then locks the chosen one and tests it (clarity ladder, guarantee test). Triggers: "positioning", "how do we position", "what category are we in", "how do we differentiate from", "our homepage is confusing", "positioning options". Run before /messaging. Not for taglines or a messaging library (use /messaging).

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

Records hypotheses, evidence and decisions when proposing, selecting, running or evaluating forecast experiments, including backtests and feature or model comparisons. Excludes routine tests and unchanged forecast operation.

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

Test and validate MaaFramework Pipeline JSON, recognition nodes, action nodes, CustomAction/CustomRecognition wiring, resource loading, and end-to-end task behavior. Use when running `run_pipeline`, checking OCR/TemplateMatch/ColorMatch ROI, validating `context.run_task()` results, auditing `action: Custom` or `recognition: Custom` registrations, or choosing the right resource-check command.

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

Designs publication figures for social-science manuscripts. Covers chart choice, axes and scales, color and accessibility, legend order, captions that carry the title, and script-based reproducibility. Use when making, revising, or critiquing a figure for a paper, such as a coefficient plot, small multiples, a distribution, a trend, a map, or a network. Finished figure sets go to figure-table-audit for end-stage QA.

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

Audits fielded survey-response data for registered elements, data quality, bot and AI-automation screening, and sample integrity, and produces an appendix-ready quality report. Use at soft launch before full field, after fielding before outcomes are analyzed, or when asked what a study did about bots and AI respondents.

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

OCRs scanned or image-only corpora with vision-language models in four phases. Triage inventories the scans, identifies script and language, and shortlists models by script, hardware, and data constraints. Evaluate selects a system by measured CER or WER against ground truth, using born-digital twins, a second reader, and decision rules set in advance. Run builds the production pipeline. Clean removes model artifacts, audits what every cleaning rule deletes, corrects with rule-based and LLM passes, and records provenance. Use when choosing an OCR model for a corpus, measuring OCR accuracy, transcribing scans at scale, or correcting raw OCR. Born-digital documents with text layers go to doc-to-markdown; runs on Leiden's ALICE cluster add vlm-ocr-alice.

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

Designs publication tables for social-science manuscripts. Covers whether a result belongs in a table at all, column order, row grouping and panels, decimal precision, standard-error and confidence-interval conventions, self-contained titles and notes, and code-generated output. Use when building or revising a regression, balance, descriptive, or robustness table, or when working with modelsummary, stargazer, gt, esttab, or booktabs. Finished tables go to figure-table-audit for end-stage QA.

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

Scaffolds or audits a social-science replication package and evaluates the manuscript and archived research objects against FAIR principles. Scaffold mode writes the folder structure, README, master.R, figure-table crosswalk, codebook, LICENSE placeholder, and .gitignore; audit mode grades the package against a pre-release checklist and audits data, code, materials, identifiers, licenses, access restrictions, and availability statements. Use when setting up or repairing a package, checking one before submission, auditing FAIR compliance, or drafting availability statements. Adapted from Yusaku Horiuchi’s replication-package-guide.

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

Operates or audits a live Qualtrics survey through the v3 APIs without disrupting fielding. Covers publish gating, quotas, flow routing, embedded data, panel-vendor redirects, read-back verification, and a read-only pre-fielding audit. Use when publishing or patching a fielding instrument, when a quota counts without blocking, when configuring panel-vendor redirects or flow gates, or when auditing a survey before launch for consent gates, force-response completeness, quotas and redirects, anti-bot instrumentation, and language-arm symmetry.

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

Drafts or audits a scientific paper’s introduction and framing — the real-world "why", an evidence audit, the funnel from theory to a falsifiable if-then with a named estimand, bridges across experiments, and a contribution list matched to the design. Use when the user asks to write, restructure, or critique an introduction, motivate or frame a paper, repair a gap-in-the-literature opening, sharpen or calibrate a contribution claim, or connect experiments into one argument. Sentence-level flow and wording are out of scope.

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

Audits a methods section against a 45-item reporting checklist synthesized from the APSA Experimental Section rubric, JARS-Quant, CONSORT, and DA-RT, covering pre-registration, recruitment, randomization and treatments, sample flow and attrition, sample-size justification, three-tier results labeling, conjoint reporting, validity, and open-science infrastructure. Use when checking whether a methods section reports enough, preparing a submission or replication archive, asking what CONSORT, JARS, or DA-RT require, or documenting a deviation from a pre-analysis plan. Writing that plan before data collection goes to pre-registration-writing.

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

Designs and diagnoses list experiments (the item count technique), covering whether indirect measurement is warranted, control-list construction against floor and ceiling effects, design variants, estimators and assumption tests in the list package, and power planning for the precision penalty. Use when the user measures a sensitive attitude or behavior and asks about list experiments, item count, unmatched count, or veiled questioning, or has an implausible prevalence estimate. Deciding whether sensitivity bias exists at all goes to survey-design.

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

Drafts a referee report for a journal editor. Produces a recommendation, claim-and-design summary, three to six decision-driving concerns, additional concerns, and a revision plan through five parallel adversarial finders, Breaker, Butcher, Shredder, Void, Situator, a Blue Team error filter, Chief Reviewer synthesis, Tone Guard legal pass, and optional confidential editor note. Use when the user has been asked to referee a manuscript. Self-audits go to paper-review-lite or presubmit, and author responses go to referee-response.

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

Turns a theory into falsifiable, pre-registerable hypotheses, covering the DGP and DAG, identification, SATE versus PATE, counterfactual and directional framing, named estimands, justified SESOIs, the choice among NHST, equivalence, interval, and minimum-effect tests, scope conditions, and primary, secondary, and exploratory tiers. Use when the user asks to turn a research question or theory into hypotheses, whether a prediction is falsifiable, what the estimand is, or how to predict a null. Framing goes to narrative-building, the plan to pre-registration-writing.

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

Runs end-stage QA on a finished figure and table set. Checks callouts, numbering, and cross-references, whether numbers in the text match the exhibits, self-contained captions and statistical notes, accessibility and production quality, and links to the SI and replication package. Values that could only be read off an image are marked for author verification rather than estimated. Use when preparing a submission. Design guidance during drafting belongs to figures and tables.

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

Writes or reviews a pre-analysis plan before data collection — registry choice (OSF, AEA RCT Registry, AsPredicted, registered reports), PAP structure, models and decision rules locked in advance, analysis code run on simulated data, contingencies for attrition, failed manipulations, and exclusions, deviation records, and timeline. Operationalizes the pre-data-collection side of DA-RT. Use when the user asks to draft or audit a pre-registration or PAP, choose a registry, decide what to lock versus leave exploratory, or handle a later deviation. Hypotheses and estimands come from hypothesis-building, post-hoc reporting from methods-reporting.

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

End-stage QA for a finished figure and table set (callouts, numbering, cross-references, text-to-exhibit consistency, captions and notes, accessibility, SI and replication linkage). Use when preparing a submission.

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

Audit fielded survey response data for registered elements, data quality, bot and AI-automation screening, and sample integrity, and emit an appendix-ready quality report. Use at soft launch or after fielding, before outcomes are analyzed.

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